create new tag
view all tags

UDS Notes

User Manual

User Manual (including a full explanation of the error mesages) can be found at


Logs etc

The msg page gives a complete list of problems in the last > 24 hr. It is updated every 15 min from MAL data which can be 0-6hr after the event.

http://www.mssl.ucl.ac.uk/~pjs1/msg.html is a copy of the msg.html page from msslje (see next paragraph). This copy doesn't need a password, is easier to access and is outside the lab's firewall. However, it is one step more difficult to generate and so slightly less likely to be there.

http://msslje.mssl.ucl.ac.uk/msg.html is the main page (accessible from selected IP addresses)

The username is uvot and password is swifthk

The data on these pages is extracted straight from the MOC and doesn't need msslje or niners ITOS processing. The top page is also small so it can be viewed on mobile phones.

It also contains pointers to a list of upcoming Malindi passes and the Master PPST.

As Flown Timelines, PPSTs

There is a more human readable version of the PPST and as-flown timelines posted on the Swift web site:


which gives links to various days schedules. If it is the current or future day, it just gives links to the PPST, if the day has past, there is a link to the as-flown as well. For example, Sept 13 is here:


ICU Data

All the ICU data dumps are found on msslje:/home/itos/archdir (updated every 6 hours) and on niners.swift.psu.edu (reached via uvotitos@uvotitos.swift.psu.edu ).

HK Plots

Usually at http://msslje.mssl.ucl.ac.uk/hk.html

If they are not available for some reason, how does the current UDS look at the plots trivially (sometimes from home on a slower broadband link)?

In an emergency

  1. we would ask Scott or
  2. if unavailable simply read the email Scott wrote on Fri Mar 11 15:04:58 2005 (see below) or
  3. just write a similar tar command and scp or ftp the result each day

"In the past, I've found it helpful to see the PNG plots Phil makes on niners. It's a hassle to find them from home on a slow connection, so I've written a script to tar up all png plots for a given day of year.

niners> cd $UVOT_ARCHDIR
niners> ./getpng 070
                      (or just)
                      (to get todays plots)

The output is written to /tmp/png.tar as indicated by the script. If you don't supply a day of year, then it uses the current day of year."

The resultant /tmp/png.tar needs to be transferred to MSSL. You can

  1. ftp to ftp:/uploads or
  2. scp to any computer that accepts incoming ssh (not MSSL) or
  3. copy to uvotitos first and then scp or ftp from that or scp to that.

The plots are simple image files in a directory structure on niners with obvious names. Scott finds it easiest from home to copy the files and look at them at leisure at home.


  1. the filename doesn't really matter
  2. the order of the files doesn't really matter and
  3. they should all be looked at

there's no point in keeping the directory structure or web page.

DPU Count Rates

From Phil's email dated 14 April 05

If the UDS sees IDPUCOUNTRATE or D_DPA_QDEPTH messages, then the UDS does the following or simply asks Phil to (since this is probably a CDS job and document says he's the CDS for the angles graph):

  1. Look at the time in the email which merely hints at when the problem happened
  2. Check the angle graphs on niners or msslje to find out when the countrate really was high.
  3. Report the countrate (stressing that it may be higher), the REAL time of the countrate, the Earth angle (increasing or decreasing) and the filter (and if possible the uvotmode) to people like Pete, Sally and uvot_cal.


You can calculate the ang separation of 2 positions using angsep


Docushare (describing ALL procedures): https://www.swift.psu.edu/docushare/dsweb/View/Collection-127

mssls7 web pages (describing "useful" procedures): http://mssls7.mssl.ucl.ac.uk/swift/docs/procedures/

The latter include all the things we need to remember about resetting parameters after a reboot and a full list of what to do for a safety circuit trip. As of 7 Nov '05, this list included

  • code_load
  • idpucountrate
  • power_on
  • reload
  • safety_circuit
  • watchdog

The official written procedures (what to do when something goes wrong) are on Docushare. After any problem they are updated, if necessary, with the latest details. That's why a few of them reference the web pages on mssls7, in particular the fast-changing things (e.g., the Earth and Moon angles during the Earth and Moon tests and the safety circuit parameters during the Safety Circuit Crisis) are there. In fact, ALL the regularly used Written Procedures refer to the mssls7 web pages, so normally uou only need to know about the mssls7 web pages. Most of the other written procedures are for things that never happen or have already happened (like commissioning and door opening).

  • Harry Anderson maintains the Written Procedures and will make changes quickly if problems are found.
  • Phil maintains the mssls7 detail.
  • Email Phil if there are any mistakes.
  • The written procedures are controlled by the FOT at the MOC.
  • The procs are version-controlled by Scott and Phil in CVS.

N.B. These procedures are merely a best-effort guide as to what to do. They are correct for all previous problems. That may NOT be correct for some future problems! They should not be followed blindly.

Hence the unwritten rules:

If at all available

  • PJS1 should authorize any commanding to the ICU
  • TSK should authorize any commanding to the DPU

This is because the MOC, ITOS and UVOT are all very complex and there many reasons why running commands might be dangerous or might lose information.

If Phil is not contactable for many hours/days, Harry Anderson is our UVOT expert at the MOC and understands the MOC, ITOS, the UVOT Written Procedures and the ITOS STOL procs very well. Always check with him first. He probably knows better than us ... seriously! The other FOT people are also good and can help.

Scott has run many of the procedures and procs in testing and in flight. Barry has been present for many of the proc runnings particularly in I&T. Howard has run some of the procs at MSSL and understands many of the telecommands.

All the FOT and Scott know where the UVOT written procedures are and know to follow them when instructed to do so. (Marg and Pete and others at the MOC also know about the written procedures.) They also have our fault table (included in the User Manual) which is for if no one can be contacted.


  • "Written Procedures" are English documents describing how to recover from problems.
  • ITOS STOL procs are computer programs in the ITOS computer language that tell ITOS what to do.

Day Number Calendars

These calendars were generated using this spreadsheet.

Non Leap Years

(also in pdf PDF format )
Non Leap Years

Leap Years

(also in pdf PDF format )
Leap Years

Last revision: r29 - 2006-05-18 - 10:04:07 - HowardHuckle
Edit | Attach | Watch | Print version | History: r29 < r28 < r27 < r26 < r25 | Backlinks | Raw View | More topic actions
Topic revision: r29 - 2006-05-18 - HowardHuckle
This site is powered by the TWiki collaboration platform Powered by PerlCopyright © 2008-2020 by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Ideas, requests, problems regarding TWiki? Send feedback