[FIBERALLOC-33] How to deal with manually provided/cached catalogues for guide star selection? Created: 21/Aug/20 Updated: 30/Sep/20 |
|
| Status: | Open |
| Project: | Target to fiber allocation and configuration |
| Component/s: | ets_shuffle |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Task | Priority: | Normal |
| Reporter: | Martin Reinecke | Assignee: | mxhf |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||||||
| Description |
|
The description of https://pfspipe.ipmu.jp/jira/projects/FIBERALLOC/issues/FIBERALLOC-28 mentions:
But also shuffle must allow for other catalogs (sdss, vizier) and manually supplied catalogs (e.g. from HSC pre-imaging).
(emphasis added). I'd like to understand better what these manually supplied catalogs look like. If they come in form of table names on a TAP-capable server, everything is fine, but if they are supplied as, e.g., FITS files (which was the case for HETDEX, if I understand correctly), I cannot really deal with them at the moment. Querying anything that is not behind an ADQL-capable front end will require quite significant changes and enhancements to the current version of the code. |
| Comments |
| Comment by rhl [ 21/Aug/20 ] |
|
Is there some reason not to load these tables into a DB as part of the observing preparation? I don't know whether you'd rather have e.g. TAP, sqlite, or postgres but it seems reasonable for this to be done outside this code. |
| Comment by Martin Reinecke [ 21/Aug/20 ] |
|
If there is an option of providing the catalogs in a way that I can access them in a way analogous to the online catalogs, I'm perfectly happy. I can't judge how much effort this would be, but if it is an acceptable solution, then we can just clarify this in the description of |