|
|
|
Matching CIAO and CALDB VersionsCIAO 4.0 requires CALDB 3.4.0 or higher to operate properly. Are your versions mismatched? Time to update CIAO and CALDB! Source Detection and Cosmic-Ray AfterglowsCIAO users who are trying to detect sources of about 10 counts or less should be aware of potential confusion with cosmic-ray afterglows that have not been removed from the data. The Cosmic-Ray Afterglows why topic explains the limitations of the current tools and describes analysis tips to help eliminate more of the afterglows. 23 Jun 2008 CALDB 3.4.5 has been released for use with CIAO 3.4 and CIAO 4.0. Information on the patch is available from the CALDB 3.4.5 Release Notes and How CALDB 3.4.5 Affects Your Analysis. 4 Jun 2008 The CXC announces the return of the Chandra/CIAO workshops. This is the sixth in a series of workshops started in 2001 aimed at helping users to work with the Chandra Interactive Analysis of Observations (CIAO) software. The 6th Chandra/CIAO Workshop will be held 20-22 October 2008 at the Chandra X-ray Center in Cambridge, MA (USA). Registration is now open! 30 May 2008 Several of the CIAO contributed scripts were updated to replace the Unix "head" and "tail" commands with the CIAO tools "dmkeypar" and "pget". A user reported script failure on Mac OS X 10.4 Intel due to incompatible syntax. 16 Apr 2008 CIAO has been patched to CIAO 4.0.2. The CIAO 4.0.2 patch enables CIAO to run on Mac OS X 10.5 (Leopard) Intel. The patch is optional for 10.4 (Tiger) Intel machines. The patch should not be applied to Linux, Solaris, or Mac PowerPC installations of CIAO. Additionally, there is an updated standalone version of ObsVis for Mac OS X Intel; see the ObsVis website for details and the download. |
Installing and Using ScriptsInstallationAll of the contributed scripts are contained in the CIAO_4.0_scripts.tar package. The scripts page describes the scripts available for download. All of the script have a help file ("ahelp <scriptname>"); some scripts also have a parameter file. The installation process is described step-by-step in the README_CIAO_scripts file. As explained in the README, the scripts are intended to be installed in the $ASCDS_INSTALL/contrib directory of the CIAO directory structure. If you do not maintain your own CIAO installation, you will have to ask your system administrator to install the package. Installing the scripts in this way provides seamless integration with CIAO: Command-line scripts will be in the user's path, S-Lang scripts and functions will be within S-Lang's search path, and ahelp and the parameter interface will function as they do with the CIAO tools. Uninstalling Old ScriptsBefore installing the a new script package, you should remove the files from previous script installations. The uninstall script is called uninstall_4.0_scripts. Please see the text of the script for usage instructions and some warnings about the uninstallation process. unix% cd $ASCDS_CONTRIB unix% ./uninstall_4.0_scripts Removing file bin/acis_bkgrnd_lookup Removing file bin/acis_fef_lookup ... Removing empty directory bin Removing empty directory param Removing empty directory share/slsh/local-packages Removing empty directory share/slsh Removing empty directory share Done! Running a ScriptThere are two general types of scripts: command-line scripts (written for the slsh, sh, ksh, and Perl interpreters) and S-Lang scripts, which are run from within a S-Lang-enabled application, such as slsh. Command-Line ScriptsWhen CIAO is started, the contributed script directory is added to the user's path (in this example, $ASCDS_INSTALL is set to /soft/ciao-4.0/): unix% echo $PATH ...:/soft/ciao-4.0/bin:/soft/ciao-4.0/contrib/bin:... This makes it possible to call the script from the command line just like a CIAO tool, without needing to specify the path: unix% merge_all Input event file(s) (): ... Note that the scripts are executable by default when they are installed, so there should not be any need to change permissions (e.g. "chmod +x merge_all") before use. S-Lang ScriptsS-Lang scripts must be called from within an interpreter, such as slsh. This example is taken from the Filtering Lightcurves thread:
slsh> () = evalfile("analyze_ltcrv.sl");
slsh> analyze_ltcrv("lc_c7.fits")
CIAO defines the $SLANG_SCRIPT_PATH environment variable, which includes the path to the scripts directory ($ASCDS_INSTALL/contrib/share/slsh/local-packages): unix% echo $SLANG_SCRIPT_PATH /soft/ciao-4.0/share/slsh/local-packages:/soft/ciao-4.0/contrib/share/slsh/local-packages Therefore, it isn't necessary to specify the path in the evalfile command. |
![]() |
The Chandra X-Ray
Center (CXC) is operated for NASA by the Smithsonian Astrophysical Observatory. 60 Garden Street, Cambridge, MA 02138 USA. Email: cxcweb@head.cfa.harvard.edu Smithsonian Institution, Copyright © 1998-2004. All rights reserved. |