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

Aligning WW3 processors with SCHSIM produce unit error #1

Open
uturuncoglu opened this issue Oct 30, 2023 · 3 comments
Open

Aligning WW3 processors with SCHSIM produce unit error #1

uturuncoglu opened this issue Oct 30, 2023 · 3 comments
Assignees
Labels
bug Something isn't working

Comments

@uturuncoglu
Copy link
Collaborator

Describe the bug
Aligning processors of WW3 with SCHSIM produce unit error since both model uses same unit numbers and they are statically defined. The could also happen in other configurations.

To Reproduce

  • Run coastal_ike_shinnecock_atm2sch2ww3 by assigning same resource to SCHSIM and WW3 like following,
MED_petlist_bounds:             0 15
ATM_petlist_bounds:             0 15
OCN_petlist_bounds:             0 15
WAV_petlist_bounds:             0 15

Expected behavior

 0:       *** WAVEWATCH III Program shell ***
 0: ===============================================
 0:  WW3 runtype is initial
 0:   Time interval :
 0: --------------------------------------------------
 0:  Starting time : 2008/08/23 00:00:00 UTC
 0: start_ymd, stop_ymd = 20080823  20080824
 0:
 0: EXTCDE MPI_ABORT, IEXIT=    60
 0:
 0:
 0: EXTCDE MSG=unit ndsm is already in use
 0:

Screenshots
N/A

Additional context
N/A

@uturuncoglu uturuncoglu added the bug Something isn't working label Oct 30, 2023
@uturuncoglu uturuncoglu self-assigned this Oct 30, 2023
@janahaddad
Copy link
Collaborator

Seems like we can close @uturuncoglu ?

@uturuncoglu
Copy link
Collaborator Author

@janahaddad It is hard to remember for me. So, I double check the existing DATM+SCHSIM+WW3 test (https://github.com/oceanmodeling/ufs-coastal/blob/feature/coastal_app/tests/tests/coastal_ike_shinnecock_atm2sch2ww3) and it seems it is still using distinct set of processors. So, maybe we could have still issue in here. I need to check it again.

@uturuncoglu
Copy link
Collaborator Author

@janahaddad There might be a memory corruption issue in there but it is better to check it again.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
Status: Backlog
Development

No branches or pull requests

2 participants