|
Linuxpops
3.01.04
Spectral Anaysis Package for Single Dish Data
|
|
Linuxpops
3.01.04
Spectral Anaysis Package for Single Dish Data
|
This complete, from scratch, rewrite of Unipops was our attempt to implement the functionality of the long since dead and unsupported Condar and a usable replacement for Line. We have not endeavored to create a one for one replacement, but a functional replacement.
Many of the commands are missing as are the advanced parser functions and scripting language. Although, a limited 'stack' looping feature and linear scripting is supported. i.e. scripts that contain known commands.
What remains is basic data analysis necessary to reduce continuum and spectral line data. Such as displaying individual scans, analyzing sky-tips, focusing and five-points. In addition, it can perform beam efficiency measurements, based on sequence scans, and analyze dual-beam switched beam maps.
On the spectral line portion most functionality of Unipops Line are implemented.
And new to Linuxpops, a robust OTF gridder and mapping analysis package.
Linuxpops uses flags for most commands to alter their behavior. If at any time you are unsure of a command, just type the command with a /h and a brief help page will display.
Every attempts has been made to remove conflicting flags, but some may have creep in.
Please let the authors know of any bugs or misbehavior encountered while using Linuxpops.
Report bugs to tfolkers@arizona.edu
Introduced in this version is the concept of environments. That is, you can be working on analyzing one source with all the search criteria set-up,and then quickly switch to another entirely different environment with one single command. And then, switch back to the first. A total of (16) environments are available.
Think of environments as completely separate instances of an analysis program, although much of the resources are shared.
Each environment contains all the search parameters necessary to single out the data sets, scans, sources, frequencies, etc. you are interested in, including the ability to ignore bad scans. You can also specify a completely different input data-file. Although, environment #0 is meant to be reserved for the on-line file. (Not strictly enforced at this time)
The compete state of your session is keep in a binary memory file that automatically loads at run-time. You can even specify a named memory file if you like; further adding to the versatility. Individual environment configurations can be saved in a text file that can be edited and reloaded when necessary.
Your command line history is saved and can be reviewed and re-executed much like a shell command parser. Each observer has their own history file.
Another innovation in LinuxPops are data holders (LP_IMAGE_INFO). These are snap-shots of reduced data.
There are 10 such holders with H0 being the normally active unit.
Data holders can be used to hold complete or intermediate results that can eventually be summed together to form a final result.
Data Holders are how you 'transfer' reduced data and information between environments.
Coupled with the ENVIRONMENT above one can, say, switch to one environment, analyze the data into holder H1, switch to another environment reduce the data into holder H2, then sum them together into holder H0 plotting the results. See the Holders documentation for further explanation.
NOTE: It is recommended that you set your terminal width to 135 characters to better match the programs output; LinuxPops can be verbose at times.
Once you are logged into the observer account, all you need to do is type startlinuxpops to start.
Start-up options are:
Linuxpops(C) >> startlinuxpops -h
Linuxpops(C) >> #
Linuxpops(C) >> # Usage: startlinuxpops [-vlrhgs] [-i init_file] [-g global_memory_file]
Linuxpops(C) >> # Where: -v Show version info and exit.
Linuxpops(C) >> # -h Show this help and exit.
Linuxpops(C) >> # -l Turn on logging. Logfile will be named: linuxpops.$(PID).log
Linuxpops(C) >> # -r Remove stale LOCKFILE before starting.
Linuxpops(C) >> # -i Load init_file upon starting.
Linuxpops(C) >> # -g Use named global_memory_file instead of default.
Linuxpops(C) >> #
Upon start-up, LinuxPops will set-up your default environment and should be ready to analyze the on-line data.
Type params to show the current search criteria. You can change each of them by using the various Search Criteria Commands. See that section under LinuxPops Command Reference.
The main search criteria commands are: freq & source. You can refine the search by selecting a single feed, or date. The freq command tells LinuxPops what frequency to select. The delfreq specifies a tolerance for frequency matching; default freq +/- 0.500 GHz for continuum and +/- 0.001 GHz for spectral line.
Once you are happy with the search criteria, type list to see a list of matching scans. List can further be refined by passing it the seq, qk5, foc, bsp, etc. argument to only show specific types of scans.
Type accum to analyse the data. In Continuum mode, this will show all ON/OFF Sequence scans that match all the criteria that you have selected.
In Spectral Line mode this will sum any BSP, PS or TP scans.
Convenience functions of the accum command are:
There is a history function in the command line parser so using the up and down cursors will allow you to peruse past commands and edit them in the command-line, then re-executing them. You can also use history manipulations such as '!get' to execute the last get command, '!102' to execute command 102 again, or '!? grep' to execute the last command that contained the word grep.
Starting LinuxPops will start a companion program called xgraphic which in turn handles all graphics functions. It does this by starting it's own instance of the gnuplot program and handles all communications back and forth with it. Essentially, gnuplot does all the actual plotting with xgraphic generating the plotting commands.
All printing is handled through gnuplot.
Copyright 2021 Arizona Board of Regents on behalf of the University of Arizona.
For commercial uses, to obtain a license to sell and or sublicense copies of the Software please contact the University of Arizona at Tech Launch Arizona: lewish@tla.arizona.edu.
Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction for non-commercial use educational and research purposes, including without limitation the rights to use, copy, modify, merge, publish, distribute, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:
The entire above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.
THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
1.0 Additional Required Provisions
1.1 Arbitration. The parties agree that if a dispute arises between them concerning this Agreement, the parties may be required to submit the matter to arbitration pursuant to Arizona law.
1.2 Applicable Law and Venue. This Agreement shall be interpreted pursuant to the laws of the State of Arizona. Any arbitration or litigation between the Parties shall be conducted in Pima County, ARIZONA, and LICENSEE hereby submits to venue and jurisdiction in Pima County, ARIZONA.
1.3 Non-Discrimination. The Parties agree to be bound by state and federal laws and regulations governing equal opportunity and non-discrimination and immigration.
1.4 Appropriation of Funds. The Parties recognize that performance by ARIZONA may depend upon appropriation of funds by the State Legislature of ARIZONA. If the Legislature fails to appropriate the necessary funds, or if ARIZONA’S appropriation is reduced during the fiscal year, ARIZONA may cancel this Agreement without further duty or obligation. ARIZONA will notify LICENSEE as soon as reasonably possible after it knows of the loss of funds.
1.5 Conflict of Interest. This Agreement is subject to the provisions of A.R.S. 38-511 and other conflict of interest regulations. Within three years of the EFFECTIVE DATE, ARIZONA may cancel this Agreement if any person significantly involved in initiating, negotiating, drafting, securing, or creating this Agreement for or on behalf of ARIZONA becomes an employee or consultant in any capacity of LICENSEE with respect to the subject matter of this Agreement.
1.8.5