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

Projection plots before and after snap.physical_units() #348

Open
wants to merge 1 commit into
base: master
Choose a base branch
from
Open

Projection plots before and after snap.physical_units() #348

wants to merge 1 commit into from

Conversation

HugoPfister
Copy link

For RAMSES, projection plots after doing snap.physical_units() gives different (and wrong) results than the ones obtained with snap.original_units().

This change seems to solve the problem.

@apontzen
Copy link
Member

Thanks! Do you understand why this mismatch is arising? It would seem to suggest a deeper problem with the units system that we should fix at source rather than in the sph module.

An example file/code snippet to reproduce the problem would be helpful to look into this further.

@HugoPfister
Copy link
Author

Hi,

I ‘tested’ the correction with a sph code and it does not work (since the size of the box is note defined)... I think the units system is okay and the problem comes from a renormalisation in the integration / Kernel2D along the LOS.

Here is a link with a ramses snapshot of a low resolution cosmological simulation. There is also a .py file to generate the 2 snapshots (in the folder) and the mean surface density, which is in both case 0.00873088291913 g cm^-2
https://github.com/HugoPfister/RamsesSim

Let me know if you need something else.

Cheers,
Hugo

On 16 Nov 2016, at 16:08, Andrew Pontzen <notifications@github.commailto:notifications@github.com> wrote:

Thanks! Do you understand why this mismatch is arising? It would seem to suggest a deeper problem with the units system that we should fix at source rather than in the sph module.

An example file/code snippet to reproduce the problem would be helpful to look into this further.


You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHubhttps://github.com//pull/348#issuecomment-260969107, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AWaLK_FJyYEtxKJrgqLlykTTLyV6JIQxks5q-xx6gaJpZM4KzuPA.

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

Successfully merging this pull request may close these issues.

None yet

2 participants