Program received signal SIGFPE: Floating-point exception - erroneous arithmetic operation. about dssat-csm-os HOT 7 CLOSED

Hi @ponraj1,

The error you are getting often means that the model is somewhere dividing by zero.

What branch/version number are you running? I think we've fixed a few of these types of errors recently. You might try pulling a more recent version to see if the error is still persistent.

Also, have you tried using a debugger (see e.g. https://cs.baylor.edu/~donahoo/tools/gdb/tutorial.html) to set a breakpoint at on line 621 of ETPHR.for? You could then inspect the values of the variables on that line and determine which values are problematic.

from dssat-csm-os.

Hi @palderman Thanks a lot for getting back to me. I am using version 4.7.5.042. I will try to find the bug using the debugger which you mentioned.

from dssat-csm-os.

Hi @palderman, I think the error happened because of the methods chosen in the model for Photosynthesis (Leaf PhotoSynthesis response curve - hourly). I have tried changing to the Canopy curve (daily), it worked.

However, this error is happening only with forage crops. It might need a check with the forage crops photosynthesis module.

Thanks for supporting me to solve the issue.

Best, Ponraj

from dssat-csm-os.

Hi @ponraj1 , were you able to run the model with a debugger? It would be helpful to know what variable is the source of the issue. Looking at the line 621 of ETPHR.for for version v4.7.42 it seems like LFMAX might be the culprit:

You might also check the value for LFMAX for the cultivar you are using.

I believe the canopy photosynthesis option for the forage model is less well tested than the leaf level option. Just keep that in mind as you proceed. @chporter, would you agree with that?

from dssat-csm-os.

@palderman , yes I think that the forage modelers are using the leaf level option.
The current CSM v4.8 has already fixed this issue. I'm looping in @fabiooliveira72, who can verify.

from dssat-csm-os.

Hi @chporter and @palderman, I will verify this. Thank you

from dssat-csm-os.

Hi @ponraj1!

I would like to know if you still have this problem.

I checked this issue with PGLEAF and it was already fixed with this commit:
8dc7c73
&&
2c5eabb

Version v4.8.0.10 was correct this issue.

We are closing this issue on Friday.

Thank you,

Fabio Oliveira

from dssat-csm-os.