Skip to content

Avoiding floating point exception in some circumstances

Lee E. requested to merge forteviot/q-e:patch-1 into develop

When options filqf & filkf are used (and fine mesh points are subsequently disabled), variables nf = 0. Sometimes this can result in a floating point error when it then tries to check the modulus within the same if statement (possibly compiler dependent?). Fixed by separating out into a new if statement.

Merge request reports