-
-
Notifications
You must be signed in to change notification settings - Fork 410
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
zone boundaries with read in models #79
Comments
FYI @wkerzendorf: @ssim - do you know the status of this? I vaguely remember that we encountered something like this during Talytha's tomography project. We should try to verify whether this issue still persists in the current version of Tardis or not before deciding about the fate of this issue.... I'll try to do that. |
Update - this issue is still relevant. I've just reproduced it with the following setup (see below). Since v_inner_boundary is equal to the second zone boundary in density.dat, a cell with zero volume is created and the plasma calculation fails - it is basically stalls in the electron density iteration, spitting out tons of warnings of the kind:
Setup
|
Started a PR (#450) to address this issue. |
Checking for zero-volume cells: Fixes issue #79
PR #450 has been merged - closing |
Problems can arise if one tries to set the inner/outer boundary value for the velocity (in the model part of the yaml file) to be very close (exactly?) at the boundary of a zone as defined by a read in ascii file (containing the density profile). Problem, I think is that one can end up with zones that have no volume. Should fix this with a check that says we can only subdivide zones from the input file if the velocity boundary is sufficiently different (above some threshold difference, or something).
The text was updated successfully, but these errors were encountered: