On Aug 18, 2010, at 9:42 AM, Matthew Smith wrote:
> Thanks for your response. I am converting to fiddle with the data in python -although I think I can do that. The problem I'm having is if I do no fiddling, so just convert an ndf to fits with ndf2fits and then straight away convert it back with fits2ndf I get the error above (ie as you put it I don't get back what I started).
>
That's not meant to happen but then again we weren't really expecting it to be tried. I'll put it on the list of things to investigate. I'm not really sure why the .MORE.JCMTSTATE extension wouldn't come back unless of course your ndf2fits command is not propagating extensions (PROEXTS parameter should be true).
I think Tom Marsh was working on an python interface to NDF so it might be easier to go that route.
> I'm loading it into python as I have a lot of spectra and thought it would be easier to automatically identify and mask bad baselines that haven't been masked and spikes in the data.
Have you tried the pipeline? When you are finished I would be extremely interested in finding out how your version compares to the pipeline version. The pipeline spends a lot of time working on automatic baseline subtraction. If your algorithm is better would you mind telling us about it?
--
Tim Jenness
|