Help Page Calts

Calts can be found at:

The following help is available, click on a part of the image or one of the links

Overview of the process page

1a. General settings; left part of the screen

Here you can login and select the object type. From top to bottom :

Settings
  • (Contact) My email adress, mail me (Willem-Jan Vriend) with any question or comments you have about CalTS.
  • (DB User) The (astro-wise) username that is used for interaction with the database. When you visit this page for the first time this will be the anonymous user awanonymous. You can click on it to log in with your own astro-wise username / password. In the login screen you can specify to 'remember' your username and password for future sessions. Then your username and password will encrypted and stored in a cookie.
  • (Help) The help pages, the page you are reading.
  • (Object type) After filling in the input parameters, click on the object type to query this type for the set parameters.

1b. Query input; upper part of the screen

Here you specify the query parameters. The parameters control which object(s) will be shown in either a graphical or tabular presentation. The selected parameters are persistent, so you can set the parameters and select different object types from the left. The header of a parameter will be greyed out if the current object type does not depend on that parameter.

Query parameters

1c. Graphical Output

The graphical output plots the timestamp ranges of all queried objects. Horizontal (left to right) the timestamp ranges go from low to high, vertical (top to bottom) the creation_date. The timestamp range is plotted as a colored bar from timestamp_start to timestamp_end. To edit timestamp ranges and the is_valid flag click on the textual timestamps. When an object is eclipsed by another object the eclipsed timestamp range will be shown in black. Graphical


1d. Tabular Output

In the tabular output screen the query results are plotted in tabular form. The columns vary from object type to object type. The columns can be clicked to sort them, the '-' indicates the column is sorted descending and the '+' for ascending sorting. Click on the filename to open the window for editing the timestamps and is_valid flag. The + or x sign in the second column indicates the presence of Comment(s) for this object. Click to add or view the comments. The is_valid flag of multiple objects can be set or unset by selecting the checkboxes in front of the objects and click the 'Make Valid' or 'Make Invalid' button at the bottom. A comment should always be provided when (in)validating objects.

Tabular


2. Editting

In the edit window the timestamps can be changed and the is_valid flag set/unset, also comments can be added to the altered objects. This can be done for one or multiple objects.

Edit Screen

3. From the command line

This section covers setting the timestamps and the is_valid flag from the command line.

On the AWE prompt timestamps and the is_valid flag can be changed. After changing these attributes the object can be commited to the database using the recommit method. Notice that only the timestamp_start, timestamp_end and the is_valid flag can be (re)commited to the database in this manner, any other attribute that is changed will not be updated in the database.

Python example adjusting timestamps and is_valid:

# WARNING : the recommit(s) have been commented out in this example,
# these will change the timestamps and is_valid of the BiasFrame in the database !!
# query for a BiasFrame
import datetime
from astro.main.BiasFrame import BiasFrame
qry = BiasFrame.instrument.name == 'WFI'
bias = qry[0]
# substract one day from the timestamps start
bias.timestamp_start -= datetime.timedelta(1)
# and set timestamp_end to far future
bias.timestamp_end = datetime.datetime(2010, 1, 1)
# and commit changes to the database
# bias.recommit()
# make the BiasFrame invalid
bias.is_valid = 0
# bias.recommit()
# make the BiasFrame valid again
bias.is_valid = 1
# bias.recommit()

Python example adding a comment:

# WARNING : the commit has been commented out in this example
# query for a BiasFrame
from astro.main.BiasFrame import BiasFrame
qry = BiasFrame.instrument.name == 'WFI'
bias = qry[0]
# make a comment
from common.log.Comment import Comment
c = Comment()
c.make('A comment text', bias)
# c.commit()