You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The example below shows a many-to-one association where the two sources in epoch 2 should both be matched with the single source in epoch 3.
Following the association logic we have implemented, this should spawn two unique sources that both trace back through the individual sources in epoch 2, as this diagram shows:
But instead forced fits have taken place forward in time and the measurements in these epochs have not been associated.
The text was updated successfully, but these errors were encountered:
* master: (30 commits)
Added explicit is not None to if statement
Reapplied line breaks
Fix for #247
Fixed number of relations query
Fixed remaining col and idx names
Changed name of mode to deruiter
Update pipeline/pipeline/association.py
Update pipeline/pipeline/association.py
Update pipeline/pipeline/association.py
Update pipeline/pipeline/association.py
Changed contains siblings column to render bool
fix query with no siblings
remove annotate, use computed metrics in db
add computation of sources metrics for UI
add fields to sources for UI stats
calculate nr images and sources, update run
add nr images and sources fields to run, help txt
Consistent trailing commas
Fix lightcurve scaling with error bars (#199)
Minor bug fix
...
# Conflicts:
# pipeline/views.py
The example below shows a many-to-one association where the two sources in epoch 2 should both be matched with the single source in epoch 3.
Following the association logic we have implemented, this should spawn two unique sources that both trace back through the individual sources in epoch 2, as this diagram shows:
But instead forced fits have taken place forward in time and the measurements in these epochs have not been associated.
The text was updated successfully, but these errors were encountered: