load_minus_flux_data() crashing 2D simulations with 3D geometry? #2086
Unanswered
FrockSaints
asked this question in
Q&A
Replies: 1 comment 2 replies
-
Can you post some (minimal) code? Have you tried debugging the crash (e.g. using |
Beta Was this translation helpful? Give feedback.
2 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
I'm trying to simulate nanoparticles in a coating.
3D seems to be working, although it's surprisingly slow (months/years when it would take a few hours in 2D), but 2D crashes when using load_minus_flux_data(). I've tried commenting out that line and it works, but I don't understand why it would cause a crash.
More precisely, an initial run is done just with air, for normalization purposes, then another one with the coating plus the nanoparticles.
According to the documentation, "In a 2d calculation, only the intersections of the objects with the xy plane are considered.". This would be ideal, but for some reason it's crashing with anything other than spheres centered at z=0.
Spheres are easy to fix, as a sphere offset from z=0 has, for the 2D simulation, an easy equivalent centered at z=0. I've already tested the 2D simulation works fine in this case. But implementing equivalents for the other objects, with arbitrary offsets and rotations, is a bit of a hassle.
Two easier alternatives would be to specify the 3D geometry, grab the z=0 slice with get_array() and initialize the 2D simulation with epsilon_input_file, or to simply normalize it by hand (probably ideal, since it's just air, but haven't looked into it for a generic source yet), but now I'm curious regarding the crash.
Advice on how to proceed and insight into this problem are much appreciated.
Apologies if the exposition was long-winded and thank you for your time.
Beta Was this translation helpful? Give feedback.
All reactions