-
Notifications
You must be signed in to change notification settings - Fork 13
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
match() live calculation and cross linking #93
Comments
Looks like there is a mismatch between the times of the two steps which are
linked? To match across different simulations, the times must match to
within a small tolerance.
|
There is indeed a small time mismatch between the two simulation time steps, at the level of 0.02 Gyr, though I am not sure how you can see that? Where is the time tolerance set in the code to see if that fixes this issue? |
The step numbers mismatch, which is why I thought of this. The tolerance is specified by |
Increasing I am still puzzled by the behaviour though. I add to increase I think there is a missing factor in the "across" direction keyword: tangos/tangos/relation_finding/multi_hop.py Lines 154 to 166 in 7f36946
to make the comparison of time steps time relative rather than absolute, as for the "backwards" and "forwards" keywords. Setting this parameter probably belongs to the config file. |
Yes, I agree the |
Fixed by #94 |
Hi,
I am having trouble with the match() live calculation command. I am trying to match halos between different simulations that have been cross linked.
The links physically exist and are stored in the database (In [2] in the following python code). The match() command works as expected to find an earlier or later halo within the same simulation (In [3] in the code). When trying to match() across simulations, the live calculation returns no result (In [4] and [5]).
I am also seeing this behaviour in the web server, for which the "Find in another simulation feature also fails".
Any ideas on what is causing this?
Martin
The text was updated successfully, but these errors were encountered: