-
Notifications
You must be signed in to change notification settings - Fork 1
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
Port puncture tracker #15
Comments
We have decided to use AMReX's particle capabilities to implement this. I have been working on this this week and what I have done is on the |
Is there an inputs file I can try? One issue might be particle id must be positive. Could you try the following changes?
|
Another patch
|
Thanks for the patches @WeiqunZhang. I had to change to calling
I've added the necessary parameters to test_params.txt in d0ab14e. However, the resolution is too low with these parameters for the tracking of the punctures to be meaningful. I've been using this as a quick test to check the code doesn't crash but to check if the results are meaningful, I've added
to the end of params_profile.txt. One question I have for you is in the case of reflective BCs where the punctures lie right on the edge (face) of the problem domain. Due to finite FP precision, they may drift very slightly outside the problem domain (but still very much within the first layer of ghost cells on the finest level). How do you think we should handle this case? I think I've seen that some of the AMReX particle infrastructure marks particles as invalid if they leave the problem domain. |
Re:
Since it's called
|
Re: reflective BC, we have something called roundoff_lo and roundoff_hi in Geometry. It's guaranteed that a number in the range of Currentl |
This depends on #2.
The text was updated successfully, but these errors were encountered: