-
Notifications
You must be signed in to change notification settings - Fork 76
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
Add PeleMP cases for soot and spray #724
Conversation
There's too many of these to run all in CI or nightly tests, but I think we should add a couple to ensure good coverage so these things don't break. Right now the Soot case is a "regression test excluded from CI". I'd propose adding "Soot-ZeroD" assuming its pretty cheap so we have something for Soot in the CI. For Spray, we should probably have "Spray-EB" and something that covers splash/breakup (Spray-A-wbreakup? - although this one looks pretty heavy, so maybe it needs to just run in the nightly). |
The Spray A with breakup is definitely too much to be part of the CI. It is intended more as a way to demonstrate how to use the breakup models. A single droplet breakup test would be much more straightforward and easier to run, if we wanted to do that. It would basically use an initial droplet file like we use in the EB spray. It would have the inputs of Spray-A-wbreakup except all of the
would be referenced with |
good idea, let me try that |
@ldowen I tried to do that case as you suggest and it is aborting. What did I do wrong? The input file is
|
I remember there was an issue with reading from ascii files for particles where you had to have an extra empty line after the last particle. It might be that? |
Now that's just plain silly. Thank you, that worked. |
I agree. You should make sure the other initial particle files have that. I meant to submit a bug report to AMReX like 3 years ago when I first discovered it and never did. Those files are typically only useful for test cases so I didn't prioritize it. |
@ldowen I am having issues with the
I have therefore excluded |
@baperry2 @jrood-nrel I think this is as ready as it will be. Can you review? |
Exec/RegTests/Spray-Jet/roi.dat
Outdated
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Do we need this full data file? Seems large.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I have no idea. @ldowen ?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I deleted a bunch of zeros that I don't think do anything
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
So sorry for the late reply, This was included to demonstrate how a roi data file can be provided. However, this is not necessary and can be removed. Instead, we can just provide a constant injection velocity and mass flow rate in the input file. Also, the roi.dat in Spray-A-wbreakup is no longer used since the jet was removed and replaced with a droplet input file.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think we should actually add back the old input file for the Spray-A-wbreakup case, and have it there as a potential demo, while also keeping the lighter weight input for testing
I'm also fine with keeping this here in order to ensure the capability to read these files continues to be tested, now that the file has been trimmed it's not so huge.
Co-authored-by: Landon Owen [email protected]