Build database table(s) for tracking anomalies about jwql HOT 6 CLOSED

@hover2pi @Johannes-Sahlmann Can I assign this one to you guys? It would be nice to ramp up a few people on database expertise on the team, so I was wondering if you could work together on this.

Here is what I am thinking: We can do this with the postgresql database we already have (see database.txt in the home directory on the admin account for credentials). We can use sqlalchemy to construct ORMs to an anomalies table in a module named database_interface.py (akin to what I have for acsql).

Probably we will want a table for each instrument, since each instrument may have different anomalies to track.

Here are the columns that I have in mind:

1. Unique ID
2. filename (the full rootname of the image that was flagged)
3. flag_date (datetime in which the anomaly was flagged in the webapp)
4. <anomaly_name_1> (Boolean flag if the image has the given anomaly)
5. <anomaly_name_2>
...
N. <anomaly_name_n>

from jwql.

@bourque Do we have a running list of anomalies to track, from WFC3 or ACS perhaps? Obviously doesn't need to be exhaustive, just something to start with. Thanks!

from jwql.

@hover2pi Here are the current anomalies that WFC3 keeps track of. Of course, some of these wont make sense for any given JWST instrument, but perhaps a good start as you suggest.

Cosmic Ray Shower
Crosstalk
CTE Correction Error
Data transfer Error
Detector/Filter Ghost
Diamond Feature
Diffraction Spike
Dragon's Breath
Earth Limb
Excessive Saturation
Figure-8 Ghost
Filter Ghost
Fringing
Guidestar Failure
IR Banding
Persistence
Prominent Blobs
Satellite Trail
Scattered Light
Other

from jwql.

@hover2pi Also, I just checked and I am also having issues connecting to the database from our dev server. I think the DB server may be down. I'm going to send in a support ticket.

from jwql.

@hover2pi The database should be back up now. The problem was that the DB server was not started properly after the VM was rebooted.

You should be able to log in from the admin account on the development server. If you find this to be annoying and need/want to be able to log into your machine, let me know and we can probably set you up with an account.

from jwql.

@bourque Yup, it works now. Thanks!

from jwql.