swiggumj / schedscrape Goto Github PK

Some thought should be given to applying different formatting rules for different choices of --printformat, then lines can be generated and printed with the generic Sched.PrintOutput([format]) function, or something like that.

Eventually it may be useful to sort scheduled observations and print them accordingly. This is not yet possible.

Mostly redundant at this point.

Should include functionality to identify observations coming up in < 24/48 hours, group sessions accordingly (by telecope), and provide email(s') text to be sent to operators. This means having a dictionary of sched blocks and command files.

It may also be nice to have other output options like LST ranges of upcoming sessions, even precise windows sources will be observed according to sched blocks/catalogs, plots, etc. This would all fall under "more verbose session info."

Add functionality that looks for existing pickle files and/or writes them (instead of web scraping). This is moving in the direction of having a Sched database. For now, pickling/unpickling astropy tables should be fine, but eventually, probably want to do this another way.

Probably this means just implementing some flag (e.g. --all) to report all sessions, if desired.

Should rethink default delimiter perhaps.

Wiki output doesn't appear to be sorted nicely within blocks, so there should be control over how to sort the entire list. Also, consecutive entries (i.e. those that run from one day to the next) should be identified and merged.

Support GBNCC project ID(s).

Add functionality to quickly output lines that can be copy/pasted into the GBNCC obs sign-up page.

Not urgent, but at some point, might want to include special merge functionality for P2945 (and other sessions?) to avoid having to do this by hand.

Also, it might be a good idea to track both merged/unmerged Sched tables. I can't think of why right now, but it's something to consider in the future.

Import statements are a jungle. Trim them down if at all possible.

Should fix so that help is displayed if argparse encounters errors.

Work on docs/info to improve ease of use.

This will be useful for effectively replacing the need for GBO helpdesk emails in planning observing for GBNCC, making pointing catalogs, etc.

Scraping the schedule Aug 19-23, my scraper is missing the first 1.5 hour session (GBT20B-362) following the receiver checkout. I'm not quite sure why this is happening, but it looks like a bug. Watch out for this in putting together GBNCC schedules.

2020 Jul 25 (MJD 59055): 15:45 - 00:00: P2780 (Session A):

Should implement a new function that deals with this better. Also, it would be nice to add something to the wiki line in non-standard cases like these to signify expected cmd file changes beforehand. Same for P2780 sessions of non-standard duration.