Hi Graham,
I made a copy/paste error in my earlier message: oracdr_profile did also call $STARLINK_DIR/etc/cshrc (not etc/login twice). ORAC-DR is installed in the recommended place on this system.
Josh said that before running ORAC-DR related commands on SCUBA-2/FTS-2 data files, we first had to run one of the oracdr_scuba2_450 (or 850) scripts. These are the items that are still failing.
I can ignore that and still run oracdr commands, which then runs for an unspecified band, but I'm concerned about the validity of doing that.
Thanks,
Matt
On 2013-01-14, at 4:32 PM, Graham Bell wrote:
>> To prepare for ORAC-DR usage, I have an oracdr_profile, which defines and undefines some environment variables, sources $ORAC_DIR/etc/login, $ORAC_DIR/etc/cshrc, and $STARLINK_DIR/etc/login, then calls oracdr_scuba2_450 or oracdr_scuba2_850, which are aliases to source $ORAC_DR/etc/oracdr_scuba2_450.csh or source $ORAC_DR/etc/oracdr_scuba2_850.csh respectively.
>
> Hello,
>
> If ORAC-DR is installed in the proper place, you shouldn't need a special oracdr_profile file. (And that could help avoid errors, eg. in the steps you listed, sourcing ${STARLINK_DIR}/etc/cshrc is missing.)
>
> If you git clone or symlink ORAC-DR into the Starlink install tree as ${STARLINK_DIR}/bin/oracdr then Starlink should find all of the ORAC-DR stuff automatically.
>
> All you ought to need to do is:
>
> setenv STARLINK_DIR /wherever/you/installed/star
> source ${STARLINK_DIR}/etc/cshrc
> source ${STARLINK_DIR}/etc/login
>
> Anyway for DateTime, as Tim said, build-modules.sh should have installed it for you. I would try running that script again and looking out for errors
>
> Best regards,
> Graham
|