Requested features, major and minor

[wyrzykow]

My ideas what needs to be added to the BH TOM in near future: (solved in Dec.2020 marked with +) (solved by Mar.2023 but in BHTOM2 with +BH2)

+BH2- add current target cadence priority (compute as on the main page) in target_detail +- how to filter on Dec, Ra? why Ra,Dec, not displayed in Filters? (Cone Search) +BH2- remove some fields in the Create Form (e.g. Sundistance)

• personalised lists of targets displayed for each user, depending on their own filter (lat, long, mag limit, sun dist), set an automatic filter applied at login +- different types of LOGINS: observers, requesters, scientists (from 2021 we will need to count the number of different users) - use privileges built-in? +- Use Orcid for logging? (not possible at the moment, but LCO will look into this later) +- form for creating an account? which then is approved by a human +- form for adding an observatory? Also approved by a human +- Google Analytics, statistics of entry, per country, viewers, etc, needed for grant reports! +BH2- In Gaia Catalog search automatically fill Gaia name and CPCS name fields +BH2- automatically identify ZTF counterpart for Gaia and vice-versa +- pre-compute images with light curves in the background and display small versions in the list +- why plotting the lc is so slow if many points are plotted? +- microlensing model on the light curve - to help predict the current magnitude
• later when we have a suite of observatories, for each telescope scheduling pre-compute exposure time per filter based on the current data
• LT-SPRAT, plus module to compute the Exp time for a given S/N (ask Doug A from Liverpool)
• Gemini will allow the ETC via TOM - add it when available
• API for weather and status per telescope?
• generate finding charts for each telescope, depending on their field-of-view, needed for Gemini triggering too +- LaTeX output: generate per target list of data taken, list of observatories, number of points, see TOMToolkit instructions +BH2- archival photometry access: Harvard plates, Gaia light curves (in 2024?), ZTF, LSST alerts, MARS, ANTARES brokers
• predict the behaviour of the event using machine learning and the model of microlensing +- possibility to download the light curve data
• option/switch ra/dec to hours/degrees, or compute it at the moment of creation using extra fields +- add galactic coordinates to the event info, compute at the moment of creation using extra fields +- sort out permissions - why loging is necessary to display a single target?
• sort out special settings for Gemini, LCO, LT to be in a separate place (import?) with all passwords protected
• why do I have to repeat all the KEYs in settings (from secret), why they are not just imported from local_settings and then ready to use in settings.py? (annoying!) +BH2- scheduling obs on facilities: display target name at the top of the form
• scheduling obs on facilities: pre-fill some of the values automatically, e.g. start date, project name
• estimate the exposure time for each instrument/facility based on the current magnitude and pre-fill it in the scheduling form
• comments on the main page - change colours, also display the most recent changes (not only comments), including new targets created, names of targets which got new follow-up observations from CPCS +BH2- change last Gaia data point to last point in the entire light curve from any source, and use this to compute observing priority
• Observatory Status: information if a given telescope is available now or what is its planned operation; programmatically accessible; Rachel Street is developing this for TOM, use and install in BHTOM

[wyrzykow]

Problems for Marco Lam to work on:

1. Liverpool Telescope plugin for SPRAT triggering
2. SPRAT spectra reading
3. SPRAT spectra processing using ASPIRED
4. If possible, install Iair's display tool for spectra
5. Gemini spectra process and display

[wyrzykow]

Problems for AKOND people (Artur K., Mikolaj K.), Przemek M. and Pawel Z.

1. maintain http://bh-tom.astrolabs.pl
2. finalize integration of CCDphot processing of images
3. Upload: allow fits image (to go to CCDPHOT then to CPCS) or instrumental photometry (to go to CPCS only).
4. add hashtag fields at upload
5. develop ORCID login