CASA Contributed Tasks: Overview: Difference between revisions
(Created page with " == Overview == This is a collection of CASA tasks to help process and analyze EVLA data. Although they are not officially supported, some authors may choose to provide contact...") |
(corrected link to CASA Cookbook) |
||
| Line 4: | Line 4: | ||
This is a collection of CASA tasks to help process and analyze EVLA data. Although they are not officially supported, some authors may choose to provide contact information. | This is a collection of CASA tasks to help process and analyze EVLA data. Although they are not officially supported, some authors may choose to provide contact information. | ||
Since they are CASA tasks, you will need to run the buildmytasks application prior to importing into CASA. See [http://casa.nrao.edu/docs/UserMan/ | Since they are CASA tasks, you will need to run the buildmytasks application prior to importing into CASA. See [http://casa.nrao.edu/docs/UserMan/UserManap8.html Appendix H of the CASA Cookbook] for a description of this process. Note that as a result of posting these files to a Wiki, the names have been changed so that the first letter is capitalized. You will need to change this to lowercase prior to running <tt>buildmytasks</tt>. Once imported, they are called like any other tasks, and will include help information within CASA. | ||
Note that you may also set up CASA to auto-import external tasks built with <tt>buildmytasks</tt>. To do this, create a directory called <tt>.casa</tt> in your home directory. Within that directory, create a file called <tt>init.py</tt> containing the line "execfile('<path to mytasks.py>')", where "mytasks.py" is created by the <tt>buildmytasks</tt> command. | Note that you may also set up CASA to auto-import external tasks built with <tt>buildmytasks</tt>. To do this, create a directory called <tt>.casa</tt> in your home directory. Within that directory, create a file called <tt>init.py</tt> containing the line "execfile('<path to mytasks.py>')", where "mytasks.py" is created by the <tt>buildmytasks</tt> command. | ||
If you would like to contribute, and do not have access to the CASA Guides WIKI, you may email Juergen Ott (jott at nrao.edu). | If you would like to contribute, and do not have access to the CASA Guides WIKI, you may email Juergen Ott (jott at nrao.edu). | ||
Latest revision as of 10:14, 11 October 2012
Overview
This is a collection of CASA tasks to help process and analyze EVLA data. Although they are not officially supported, some authors may choose to provide contact information.
Since they are CASA tasks, you will need to run the buildmytasks application prior to importing into CASA. See Appendix H of the CASA Cookbook for a description of this process. Note that as a result of posting these files to a Wiki, the names have been changed so that the first letter is capitalized. You will need to change this to lowercase prior to running buildmytasks. Once imported, they are called like any other tasks, and will include help information within CASA.
Note that you may also set up CASA to auto-import external tasks built with buildmytasks. To do this, create a directory called .casa in your home directory. Within that directory, create a file called init.py containing the line "execfile('<path to mytasks.py>')", where "mytasks.py" is created by the buildmytasks command.
If you would like to contribute, and do not have access to the CASA Guides WIKI, you may email Juergen Ott (jott at nrao.edu).
