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

An error occurred while running test #1292

Closed
May0048 opened this issue Oct 15, 2024 · 15 comments · Fixed by #1294
Closed

An error occurred while running test #1292

May0048 opened this issue Oct 15, 2024 · 15 comments · Fixed by #1294

Comments

@May0048
Copy link

May0048 commented Oct 15, 2024

The following error occurred when we ran the case in the guide. May I ask what caused it? The file is as follows
spinup.txt
1728985411401

@hgopalan
Copy link
Contributor

The error message is incomplete. Can you dump the detailed error message? It is unclear what went wrong from the snapshot.

@May0048
Copy link
Author

May0048 commented Oct 15, 2024

The error message is incomplete. Can you dump the detailed error message? It is unclear what went wrong from the snapshot.
spinuo_c.txt

This is all the operational message.

@hgopalan
Copy link
Contributor

This is your error message: ParmParse::sgetarr ParmParse::sgetarr(): sampling.labels not found in table

Add the line

sampling.labels = xy-domain xz-domain

Always look for "not found" in the log file as a first check and it should solve your issues.

@May0048
Copy link
Author

May0048 commented Oct 15, 2024

This is your error message: ParmParse::sgetarr ParmParse::sgetarr(): sampling.labels not found in table

Add the line

sampling.labels = xy-domain xz-domain

Always look for "not found" in the log file as a first check and it should solve your issues.

Thanks for your reply, another error occurred after I corrected it. After checking the input file, I think the point is not outside the computational domain. The following is the running message.spinuo_c1.txt

@marchdf
Copy link
Contributor

marchdf commented Oct 15, 2024

yup that's the correct interpretation of that error message. Somehow you defined your planes such that they have points outside of the domain. I don't see how you defined them or the domain size but if you post those, we can help you figure that out.

@hgopalan
Copy link
Contributor

hgopalan commented Oct 15, 2024

The definition seems fine in spinup.txt.

@marchdf Are there any constraints on the sampler near domain boundaries. The bounds are [0,2560]X[0,2560]X[0,1280] and the plane goes until 2550 in X and Y and 1270 in Z but dx=dy=dz=20. You think this corner point can be an issue?

@marchdf
Copy link
Contributor

marchdf commented Oct 15, 2024

missed that, thanks. Going to run it locally and see if I can figure that out.

@May0048
Copy link
Author

May0048 commented Oct 15, 2024 via email

@hgopalan
Copy link
Contributor

If you do not need the corners you can reduce 2550 to 2500 and 1270 to 1200 and try. It should run without any issue.

@marchdf
Copy link
Contributor

marchdf commented Oct 15, 2024

@May0048 I have fixes to those files in PR #1293. Those files should work now.

@marchdf
Copy link
Contributor

marchdf commented Oct 15, 2024

@hgopalan it's not the high corners that are a problem, it's the low ones.

@marchdf
Copy link
Contributor

marchdf commented Oct 15, 2024

Ok the fix I am happy with is in #1294

@marchdf marchdf mentioned this issue Oct 15, 2024
14 tasks
@May0048
Copy link
Author

May0048 commented Oct 15, 2024

Ok the fix I am happy with is in #1294

Thank you for your answer. I understand what you said. Now, if I use x, y = 0, 0 as the sampling origin, do I need to recompile AMR-Wind?

@moprak-nrel
Copy link
Contributor

Since the fix involved changes to the code, I would update to the latest main branch and recompile AMRWind before you run your case again.

@May0048
Copy link
Author

May0048 commented Oct 15, 2024

Since the fix involved changes to the code, I would update to the latest main branch and recompile AMRWind before you run your case again.

Thank you for your reply. I understand what you mean,now.

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

Successfully merging a pull request may close this issue.

4 participants