| | 1 | ==Notes== |
| | 2 | |
| | 3 | 2007.02.08 : running simtest from scratch for ipp account |
| | 4 | |
| | 5 | * needed to setup ssh key : chmod 755 ~ipp was needed |
| | 6 | * needed to setup .ipprc and .ptolemyrc : no errors were generated |
| | 7 | * needed to start mysql : no error was generated |
| | 8 | |
| | 9 | * '''the CAMERA (defined by FPA.INSTRUMENT when supplied via inject_test.pl) must correspond to the ipp/config camera''' |
| | 10 | * '''need to add an entry for detRun in ippMonitor''' |
| | 11 | |
| | 12 | |
| | 13 | == Example == |
| | 14 | |
| | 15 | Step-by-step example for running a set of simulated images through the IPP. |
| | 16 | |
| | 17 | The (TBD) tarball contains [wiki:Http://kiawe.ifa.hawaii.edu/Elixir/Ohana/IPP-subsystems_pantasks http://kiawe.ifa.hawaii.edu/Elixir/Ohana/IPP-subsystems pantasks] scripts which will build a set of fake images, add them the to IPP database, and then run the different stages of the IPP on those images. |
| | 18 | |
| | 19 | Here are notes for the steps needed to get this example running from scratch. |
| | 20 | |
| | 21 | * Install all IPP software (see INSTALL guide in the ipp tarball) |
| | 22 | |
| | 23 | * Install ippMonitor software on web host machine (see INSTALL notes: some hardwired entries must be set) |
| | 24 | |
| | 25 | * create the admin database and database user (dbadmin is in ipp/ippTools/ippMonitor, not installed) |
| | 26 | dbadmin init (dbserver) (dbuser) (dbpassword) |
| | 27 | dbadmin init alala ipp PASS |
| | 28 | |
| | 29 | * add client machine regexes to the database as needed: |
| | 30 | dbadmin client (dbserver) (dbuser) (dbpassword) |
| | 31 | dbadmin client 128.171.177.% alala ipp PASS |
| | 32 | |
| | 33 | * create the database for this project |
| | 34 | dbadmin db (dbname) (dbserver) (dbuser) |
| | 35 | dbadmin db simtest alala ipp |
| | 36 | |
| | 37 | * create a user account for ippMonitor |
| | 38 | dbadmin user (username) (password) (dbserver) (dbuser) |
| | 39 | dbadmin user eugene foobar alala ipp |
| | 40 | |
| | 41 | * copy ipp/config/ipprc.config to ~/.ipprc |
| | 42 | |
| | 43 | * edit .ipprc to add DATAPATH (where data is stored) and database entries: |
| | 44 | DBSERVER, DBUSER, DBPASSWORD, DBNAME (DBPORT is optional) |
| | 45 | |
| | 46 | * create the database tables |
| | 47 | pxadmin -create |
| | 48 | or |
| | 49 | pxadmin -recreate |
| | 50 | |
| | 51 | * start pantasks to create the simulated data (you may also use mana or dvo to run these commands). this should be done in the directory containing the tarball. pantasks will provide a user prompt. pantasks commands below are prefixed with the pantasks prompt (pantasks:) |
| | 52 | pantasks |
| | 53 | |
| | 54 | * create the simulated data and inject into the db: |
| | 55 | pantasks: input sim.pro |
| | 56 | pantasks: init |
| | 57 | |
| | 58 | * go to the ippMonitor web page root and login to your user account |
| | 59 | |
| | 60 | * select the project (under Select Project) |
| | 61 | |
| | 62 | * cd to the ipp/ippTasks directory to run pantasks on the database data |
| | 63 | |
| | 64 | * edit ipp/ippTasks/pantasks.pro to reflect your installation |
| | 65 | set $LOGDIR to point at your datapath |
| | 66 | edit init.controller to include your machines |
| | 67 | |
| | 68 | * start pantasks again |
| | 69 | pantasks |
| | 70 | |
| | 71 | -- work in progress -- |
| | 72 | |
| | 73 | (run phase0 : currently we load the tasks as needed; this must be fixed) |
| | 74 | pantasks: input pantasks.pro |
| | 75 | pantasks: init.controller |
| | 76 | pantasks: load.tasks |
| | 77 | |
| | 78 | * create a bias run: |
| | 79 | dettool -simple -definebyquery -det_type bias -exp_type bias |
| | 80 | (etc) |
