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
I guess that at some point there were plans to use the extra column of type spoint(ra, dec) which is indexed and then, it can be used instead of ra, dec. I'm not quiet sure whether the implementation was completed. The code in question is
IMHO, the feature is obsolete because the indexes can be created directly for the spoint() expression. Meaning that instead of creating a new column pos as spoint(ra, dec), creating an index for it and then trying in some hacky way to replace spoint(ra,dec) with the indexed column, we just create an index as
Createindexschema_table_spoint_ra_deconschema.table using gist (spoint(RADIANS(ra), RADIANS(dec)));
No need to create an extra column in the database and no need to connect ra/dec with the spoint(ra,dec) in the translated query.
Removing this feature would simplify daiquiri and handling of the database.
The text was updated successfully, but these errors were encountered:
Yes, we have already tested (and still using) the index spoint(RADIANS(ra), RADIANS(dec)) for gaia DR3. In the case of the cone search, the new solution is even faster (~3x).
I guess that at some point there were plans to use the extra column of type spoint(ra, dec) which is indexed and then, it can be used instead of ra, dec. I'm not quiet sure whether the implementation was completed. The code in question is
daiquiri/daiquiri/query/process.py
Lines 178 to 185 in 5ae2a14
daiquiri/daiquiri/query/utils.py
Lines 132 to 148 in 5ae2a14
IMHO, the feature is obsolete because the indexes can be created directly for the
spoint()
expression. Meaning that instead of creating a new columnpos
asspoint(ra, dec)
, creating an index for it and then trying in some hacky way to replace spoint(ra,dec) with the indexed column, we just create an index asNo need to create an extra column in the database and no need to connect ra/dec with the spoint(ra,dec) in the translated query.
Removing this feature would simplify daiquiri and handling of the database.
The text was updated successfully, but these errors were encountered: