Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Floating-Point Exception Errors When Running Inlet Refined Test in COAWST 3.8 #363

Open
Pbarbosa92 opened this issue Feb 5, 2025 · 1 comment

Comments

@Pbarbosa92
Copy link

I'm trying to compile and run COAWST (version 3.8) for the Inlet Refined test, but I’m encountering errors during execution.

Observed Behavior

  1. Initially, I receive the following warning:
    MCT::m_MCTWorld::initm_MCTERROR:  MCTWorld has already been initialized...Continuing  
    MCT::m_MCTWorld::initm_MCTERROR:  MCTWorld has already been initialized...Continuing  
    
  2. After some time, the simulation prints this erros (but continues):
    Note: The following floating-point exceptions are signalling: IEEE_INVALID_FLAG IEEE_DIVIDE_BY_ZERO IEEE_UNDERFLOW_FLAG  
    Note: The following floating-point exceptions are signalling: IEEE_INVALID_FLAG IEEE_OVERFLOW_FLAG IEEE_UNDERFLOW_FLAG  
    

Steps Taken

I compiled COAWST and its dependencies following the standard procedure:

  • Built SCRIP_COAWST
  • Compiled mct
  • Installed mct
  • Ran the build_inlet_refined.sh script
  • Executed the simulation with:
    mpirun -np 2 coawstM Projects/Inlet_test/Refined/coupling_inlet_test_ref3.in  

Logs and Build Files

For reference, here are the relevant logs and scripts:

run_inlet_refined_simulation.txt

Has anyone encountered similar issues? Any guidance would be greatly appreciated!

Thanks in advance for your help.

@jcwarner-usgs
Copy link
Collaborator

those are just warnings. i see them all the time.
1 the MCT init comes up because the 2nd grid goes to init and MCT says we did this already. so it is ok. just a warning.
2 the IEEE floating is just another warning. I dont think it is a problem.

suggest you just keep moving forward!
let me know if have any other issues.
-john

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants