[Isocops] The grind

Geoffrey B. Crew gbc at space.mit.edu
Fri May 14 09:28:10 EDT 2010


2 comments:

The rlist-ena thing is only needed if you need to have it on the
web *right*away*.  The routine cron rsync will get it there naturally
in a few hours.  (I've always let it happen that way.)

As for looking at it (in this age of more operators) you could consider
having a rotating responsibility (orbit % N) for who is checking.  That
has the advantage that what one person misses will be caught by another.

-- 

		Geoff (gbc at space.mit.edu)

On Fri, May 14, 2010 at 08:47:01AM -0400, Roland Vanderspek wrote:
> 
> Since Paul has done the good times, we need to grind
> 
> ena @) ibex_gbc
> Using ISOC version 3.3 with IBEX_ROOT=/home/gbc/IBEX/sw
> IBEX_HOME is set to /home/gbc/IBEX
> ena @) cd $IBEX_CRON/scripts
> ena @) science_prods.sh test hi lo sset 0076
> <lots of output>
> 
> Recall that I did 'science_prods.sh cron main 0076' yesterday, so we can skip that step here.
> 
> ena @) science_prods.sh cron hi lo sset 0076
> <lots of output>
> 
> At this point, ena should be full of data products.  To propagate to the web (and everywhere else), you need to do
> 
> ena @) $IBEX_CRON/cronswitch.sh rlist-ena
> 
> cronswitch.sh is using /home/gbc/IBEX/sw/i686-3.3/bin/isoc.sh for setup
> ...done.
> 
> ...and we're good to go, I think.
> 
> What's missing now is a procedure for someone to go look at the data and confirm that it's OK.  We talked about it at the ISOC telecon and gave the AI to Nathan.
> 
> Roland


More information about the Isocops mailing list