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

Issues with AMR: #204

Open
smarandeshmukh opened this issue Aug 20, 2018 · 0 comments
Open

Issues with AMR: #204

smarandeshmukh opened this issue Aug 20, 2018 · 0 comments

Comments

@smarandeshmukh
Copy link

I have been unable to make raytracing work with simple AMR grids. I use the same example as in #203. I get a segmentation fault with the following:
#3 0x4A7E99 in __grid_geometry_specific_MOD_find_position_in_grid at grid_geometry_amr.f90:531 #4 0x4A7C26 in __grid_geometry_specific_MOD_find_cell_position at grid_geometry_amr.f90:559 #5 0x4A7CE2 in __grid_geometry_specific_MOD_find_cell at grid_geometry_amr.f90:550 #6 0x4A79FB in __grid_geometry_specific_MOD_place_in_cell at grid_geometry_amr.f90:565 #7 0x4D7F4B in __peeled_images_MOD_peeloff_photon at images_peeled.f90:152 #8 0x4EDF0D in __iteration_raytracing_MOD_do_raytracing at iter_raytracing.f90:121 #9 0x4EF18C in MAIN__ at main.f90:299
This happens after the normal imaging process has been completed. Has anybody else encountered something along these lines? A cursory glance suggests that Hyperion can't correctly identify in which cell the source resides in.

Thanks

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

No branches or pull requests

1 participant