[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: A Little Project
I would offer a suggestion. Make sure you only encode the column
numbers in one location, and use that variable (maybe you are already
doing this) in the rest of the script.
Then, if you wanted to, use A*p*p*C*o*n*f*i*g (Perl module, * modified to get
through the TASS filter...), or some other perl module which
read config files, to grab the column information needed, and place
into those previously used variables. I can throw a script someone's way
which uses A*p*p*C*o*n*f*i*g if you want to try that.
Date sent: Sat, 08 Jun 2002 13:19:35 -0500
To: Tom Droege <email@example.com>,
firstname.lastname@example.org From: Tom Droege
<email@example.com> Subject: Re: A Little Project
> Since someone might work on the ws output, let us agree that the
> star number that matches the collect_stars output will always be in
> column 1 and the ws statistic in column 10 as they are now. That
> way improvements can be made to the ws output to add hexadecimal
> output and Rich Knowles can use ws output as input to his plotting
> We then operate with:
> .cal files which come out of MR's pipeline
> collected files which come out of collect_stars
> ws files
> The cal files are processed by collect_stars
> The output of collect_stars is processed by ws
> One then runs selectun which looks at the collect_stars output to
> get raw data and ws output select which raw data files to plot. How
> does this sound to everyone?
> Tom Droege
> At 11:12 AM 6/8/02 -0500, you wrote:
> >Seems like VisieR does not like decimal degrees.
> >Here is a nice little project for someone. Take the wsv3.pl that I
> >put on DS23 and fix it up to put out hexadecimal notation for
> >position. I recall that the version I sent out also had a
> >programming error and puts out zeros for the error values. I had
> >added the V and I values and the errors so that I had all the
> >information I needed in one place. You might fix the error problem
> >also. I assume this is all OK with Doug. Please object Doug if
> >you don't want people working on your code. Then put the corrected
> >code up on the tass site.
> >The ws output then can be the working list for examining stars from
> > particular run. As I mentioned in the past, it is really best to
> >run ws on each individual run since when runs are grouped together,
> >small variations from run to run produce large ws statistic. So I
> >think it best to first look at each individual run. One can find a
> >few more variables this way.
> >Tom Droege
------- End of forwarded message -------