EIS Master Study Database

Saving the EIS Master Study Database on the MSSL server

The purpose of this is to put the updated master database onto the MSSL server so that:

• David Brooks (dhbrooks.work@gmail.com) can copy it to ISAS and install it there.
• SolarSoft can copy it and update it's own server.

Before you start this procedure make sure you have the latest password for the user solarb on the MSSL cluster. Louisa (louisa.bradley@ucl.ac.uk) is the guardian of this password and shares it via e-mail.

Procedure

1. On a machine other than the EGSE, log onto the cluster (msslaac for example) as user solarb in an open exterm window.
   Type:
   • ssh solarb@msslaac ↩
   Enter the password when requested.

2. On the cluster machine change directory to the where the files will be served from.
   In the xterm type:
   • cd /disk/ftp/projects/solarb/staging ↩

   This takes you to the correct directory on the server.

3. Backup the existing plan.
   In the xterm type:
   • make backup ↩

4. Copy the planning files from msslqm. This step will ask for solarb's password on msslqm twice (Note: this is the password for the solarb user on msslqm, not msslaac).
   In the xterm type:
   • make fetch ↩
   • Enter password for user solarb on msslqm ↩
   • Enter password for user solarb on msslqm ↩

5. Install the new database where solarsoft can see it.
   In the xterm type:
   • make install ↩

   The image below shows what the output will be like.

   

6. There is a text file (planning_db.txt) which holds the details for each update. Edit this with emacs or vi to keep it up to date. It's not essential but it's nice to keep a record of what's happened.

7. Logout from the cluster machine.
   In the xterm type:
   • exit ↩

8. E-mail David Brooks (dhbrooks.work@gmail.com) that there is a new database on the MSSL server ready for upload to ISAS. That will make him a happy bunny...
   Optional: the study proposer may also be emailed, informing them that the study has been verified and is available to the planners.