http://ovsa.njit.edu//wiki/api.php?action=feedcontributions&feedformat=atom&user=GnitaEOVSA Wiki - User contributions [en]2026-04-18T01:04:18ZUser contributionsMediaWiki 1.38.1http://ovsa.njit.edu//wiki/index.php?title=EOVSA_Data_Analysis_Tutorial&diff=4467EOVSA Data Analysis Tutorial2019-05-29T16:13:49Z<p>Gnita: /* Spectral Fitting with GSFIT */</p>
<hr />
<div>=Browsing and Obtaining EOVSA data=<br />
[[file:fig-browser.png|thumb|right|500px|Browsing EOVSA data in RHESSI Browser]]<br />
<br />
Currently the most convenient way for browsing EOVSA data is through the [http://sprg.ssl.berkeley.edu/~tohban/browser/ RHESSI Browser]. First, check the "EOVSA Radio Data" box on the data selection area (top-left corner). Then select year/month/date to view the overall EOVSA dynamic spectrum. Note if a time is selected at early UTC hours (e.g., 0-3 UT), it will show the EOVSA dynamic spectrum from the previous day. Also note that EOVSA data were not commissioned for spectroscopic imaging prior to April 2017. An example of the overview EOVSA dynamic spectrum for 2017 Aug 21 is shown in the figure on the right.<br />
<br />
The overview EOVSA dynamic spectra are from the median of the <b>uncalibrated</b> cross-power visibilities at a few short baselines, which are not (but a good proxy of) the total-power dynamic spectra. The effects of spatial information blended in the cross-power visibilities can be clearly seen as the "U"-shaped features throughout the day, which are due to the movement of the Sun across the sky that effectively changes the length and orientation of the baselines. Flare times can be easily seen in the EOVSA dynamic spectra, which usually appear as vertical bright features across many frequency bands. More information can be found on [http://ovsa.njit.edu/data-browsing.html this page].<br />
<br />
We are currently working on a pipeline to create quicklook full-disk images for implementation at the RHESSI Browser in a way similar as the RHESSI quicklook images. Please stay tuned.<br />
<br />
Once you identify the flare time, you can find the full-resolution (1-s cadence) uncalibrated visibility files (in Miriad format) at [http://www.ovsa.njit.edu/fits/IDB/ this link]. Each data file is usually 10 minutes in duration. Name convention is YYYYMMDD/IDBYYYYMMDDHHMMSS, where the time in the file name indicates the start time of the visibility data. <br />
<br />
=Calibrating EOVSA data=<br />
<br />
*<b>Calibration</b>: Calibrating EOVSA data is an involved process. We are currently working on a semi-automatic pipeline for calibrating the visibility data. At this moment, however, please contact the EOVSA team if you wish to have calibrated visibility data for a specific event. In the near future, we envision the pipeline-calibrated visibility data to be available for download on a regular basis.<br />
<br />
*<b>Self-calibration</b>: For improving the quality of the imaging, self-calibration is usually needed. This is still a work-in-progress, but we have had some successful practice in self-calibrating some flare events. Please refer to [[Self-Calibrating Flare Data]] for examples and detailed discussions on our current practice for self-calibrating EOVSA flare data.<br />
<br />
=Analyzing EOVSA data=<br />
==Software==<br />
We have developed two packages for EOVSA data processing and analysis:<br />
* [https://github.com/suncasa/suncasa SunCASA] A wrapper around [https://casa.nrao.edu/ CASA (the Common Astronomy Software Applications package)] for synthesis imaging and visualizing solar spectral imaging data. CASA is one of the leading software tool for "supporting the data post-processing needs of the next generation of radio astronomical telescopes such as ALMA and VLA", an international effort led by the [https://public.nrao.edu/ National Radio Astronomy Observatory]. The current version of CASA uses Python (2.7) interface. More information about CASA can be found on [https://casa.nrao.edu/ NRAO's CASA website ]. Note, CASA is available ONLY on UNIX-BASED PLATFORMS (and therefore, so is SunCASA). <br />
* [https://github.com/Gelu-Nita/GSFIT GSFIT] A IDL-widget(GUI)-based spectral fitting package called gsfit, which provides a user-friendly display of EOVSA image cubes and an interface to fast fitting codes (via platform-dependent shared-object libraries). <br />
<br />
For this tutorial, there are two approaches in accessing our software packages: <br />
* 1. Through our '''Amazon Cloud server'''. See [[#Using Software on AWS server|Section 3.1.1]] for detailed instructions.<br />
* 2. Install on '''your own machine'''. See [[#SunCASA Installation|Section 3.1.2]] (SunCASA) and [[#GSFIT Installation|Section 3.1.3]] (GSFIT) for instructions.<br />
<br />
===Using Software on Amazon Cloud Server===<br />
We use an [https://aws.amazon.com/lightsail/ Amazon AWS Lightsail] cloud server for lightweight data processing and testing purposes. The server has 2 CPUs, 8 GB RAM, and 160 GB SSD storage. It runs CentOS 7 (1901-01) Linux.<br />
<br />
''NOTE: the guest account is <b>ONLY INTENDED FOR THE EOVSA TUTORIAL, WHICH WILL BE DISABLED SHORTLY AFTER THE RHESSI WORKSHOP </b> (you will be notified prior to that). '' If you wish to continue using the server for testing purposes after the tutorial, please contact [mailto:bin.chen@njit.edu Bin Chen] to set up a personal account. <br />
<br />
''DISCLAIMER: We are NOT RESPONSIBLE for any loss, damage, or leak of your personal data on the server.''<br />
* Obtain SSH Key to the guest account from [mailto:bin.chen@njit.edu Bin Chen]<br />
* Put it under a secure location on your own machine.<br />
* Follow remaining directions depending on your client machine.<br />
<br />
====Connecting via command line====<br />
* Edit the permission of the SSH key and the directory you choose to place it. Here I use ~/.ssh as an example (create it first by ''mkdir ~/.ssh'' if it does not exist.)<br />
<pre><br />
chmod 700 ~/.ssh<br />
chmod 400 ~/.ssh/guest-virgo.pem<br />
</pre><br />
* Log on to AWS server (password-less)<br />
<pre><br />
ssh -X -i ~/.ssh/guest-virgo.pem guest@virgo.arcs.az.njit.edu<br />
</pre><br />
Now you are connected to '''virgo'''.<br />
<br />
====Connecting via Windows (MobaXterm)====<br />
Recommend to use "Documents\MobaXterm\home\.ssh", which should exist if you have already installed the free MobaXterm[https://mobaxterm.mobatek.net/].<br />
* Create new session, click SSH, enter virgo.arcs.az.njit.edu for Remote host, guest for username.<br />
* On advanced SSH settings tab, click Use private key, navigate to and select file guest_virgo.pem<br />
* Close setup window and click the new session's icon, which will log you in.<br />
<br />
====Startup SunCASA and sswIDL====<br />
Once you are connected to '''virgo''', you will have access to SunCASA and GSFIT (included in the sswIDL installation). To not interfere with others (who share the same "guest" account), please <b>create your own directory and work under it</b>. For easier identification, please kindly use <b>the initial of your first name and your full last name as the name of your directory</b> (here "bchen" is used as an example). <br />
<pre><br />
[guest@ip-172-26-5-203 ~]$ mkdir bchen<br />
[guest@ip-172-26-5-203 ~]$ cd bchen<br />
</pre><br />
To enter SunCASA<br />
<pre><br />
[guest@ip-172-26-5-203 ~/bchen]$ suncasa<br />
</pre><br />
To enter sswIDL<br />
<pre><br />
[guest@ip-172-26-5-203 ~/bchen]$ sswidl<br />
</pre><br />
<br />
===[[SunCASA Installation]]===<br />
Please [http://www.ovsa.njit.edu/wiki/index.php/SunCASA_Installation follow this link] for details regarding installation of SunCASA on your own machine (only available on Unix-bases OS). This will take you to another page.<br />
<br />
===[[GSFIT Installation]]===<br />
Please [http://www.ovsa.njit.edu/wiki/index.php/GSFIT_Installation follow this link] for details regarding installation of GSFIT on your own machine (which supports multiple platforms). This will take you to another page.<br />
<br />
==Example Data and Scripts==<br />
In this tutorial, we will demonstrate steps for spectral imaging (self-)calibrated visibility data for a C-class flare on 2017 Aug 21 at ~20:20 UT ([[#Spectral Imaging with SunCASA|Section 3.3]]), followed by a tutorial on visualizing and analyzing the resulting spectral imaging cube ([[#Spectral Fitting with GSFIT|Section 3.4]]). <br />
<br />
The visibility data can be accessed by<br />
* Downloading from [https://drive.google.com/open?id=1ZMCY9Y3FTv-m0QFyBBwrvqaSuS5pAc3l this Google Drive link]. <br />
* If you are on our AWS cloud server "virgo" (means for accessing the server are discussed in [[#Using Software on AWS server|Section 3.1.1]]), it is located at /common/data/eovsa_tutorial/IDB20170821201800-202300.4s.slfcaled.ms. <br />
<br />
''To reduce the amount of data for this tutorial, the time resolution has been reduced by a factor of 4, to 4 s per sample. The actual time resolution available is 1 s.'' If you are on virgo, please copy it over to your own working directory that you created earlier under the guest account (e.g., ~/bchen/).<br />
<br />
<pre style="background-color:#FCEBD9;"><br />
cd ''your_working_directory''<br />
cp -r /common/data/eovsa_tutorial/IDB20170821201800-202300.4s.slfcaled.ms ./<br />
</pre><br />
<br />
Example scripts for doing the analysis covered in this tutorial are available as [https://github.com/binchensun/eovsa-tutorial/tree/master/rhessi18 this Github repository]. On Virgo, the scripts can be found under /common/data/eovsa_tutorial/.<br />
<br />
==Spectral Imaging with SunCASA==<br />
EOVSA data is handled in [https://casa.nrao.edu CASA] tables system, known as a Measurement Set (MS). The actual visibility data are stored in a MAIN table that contains a number of rows, each of which is effectively a single timestamp for a single spectral window and a single baseline. Within SunCASA, in addition to everything already available in CASA, you have access to additional tools that allow you to explore and utilize the new radio dynamic spectroscopic imaging data from EOVSA. We also had success in using SunCASA for analyzing data from the [https://science.nrao.edu/facilities/vla Karl G. Jansky Very Large Array]. The steps are very similar to those described here.<br />
To start SunCASA, use:<br />
<pre style="background-color:#FCEBD9;"><br />
suncasa<br />
</pre><br />
Within SunCASA, you are under the IPython environment. Everything you know about (I)Python should be applicable here. The installation comes with frequently used packages including Matplotlib, Numpy, SciPy, AstroPy, SunPy. However, it is not very intuitive to add (compatible) Python packages within (Sun)CASA. If you choose to do so, you may want to check [http://docs.astropy.org/en/stable/install.html#installing-astropy-into-casa this page] on how to install AstroPy (which is not originally shipped with CASA) within CASA. This method is generally applicable to adding other packages (but not thoroughly tested). If you need some specific packages for your analysis, and it does not require direct interaction with (Sun)CASA, we recommend you to use the standard Python environment. On Virgo, we have installed Anaconda 3, which can be accessed by, e.g., typing "ipython" in a terminal window.<br />
<br />
===Cross-Power Dynamic Spectrum===<br />
The first module we introduce is [https://github.com/suncasa/suncasa/blob/master/utils/dspec.py ''dspec'']. This module allows you to generate a cross-power dynamic spectrum from an MS file, and visualize it. You can select a subset of data by specifying a [https://casa.nrao.edu/Release3.3.0/docs/UserMan/UserMansu112.html time range], [https://casaguides.nrao.edu/index.php/Selecting_Spectral_Windows_and_Channels spectral windows/channels], [https://casaguides.nrao.edu/index.php/Antenna/Baseline_Selection_Syntax_with_or_without_Autocorrelations antenna baseline], or [https://casa.nrao.edu/Release3.3.0/docs/UserMan/UserMansu113.html uvrange]. The selection syntax follows the ''CASA'' convention. More information of CASA selection syntax may be found in the above links or the [https://casa.nrao.edu/casadocs/casa-5.4.0/data-selection/data-selection-in-a-measurementset Measurement Selection Syntax].<br />
[[file:fig-dspec.png|thumb|right|300px|Figure 1: EOVSA cross power dynamic spectrum at stokes XX and YY]]<br />
<pre style="background-color: #FCEBD9;"><br />
from suncasa.utils import dspec as ds<br />
import matplotlib.pyplot as plt<br />
## define the visbility data file<br />
msfile = 'IDB20170821201800-202300.4s.slfcaled.ms' <br />
## define the output filename of the dynamic spectrum <br />
specfile = msfile + '.dspec.npz' <br />
## select relatively short baselines within a length (here I use 0.15~0.5km), <br />
## and take a median cross all of them (with the domedian parameter)<br />
## alternatively, you can use the "bl" parameter to select individual baseline(s)<br />
uvrange = '0.15~0.5km'<br />
## this step generates a dynamic spectrum and saves it to specfile<br />
dspec=ds.get_dspec(vis=msfile, specfile=specfile, uvrange=uvrange, domedian=True)<br />
## dspec is a Python dictionary that contains the resulting dynamic spectrum. <br />
## A copy is saved in "specfile" as a numpy npz file.<br />
## Other optional parameters are available for more selection criteria <br />
## such as frequency range ("spw"), and time range ("timeran")<br />
## Use "ds.get_dspec?" to see more options<br />
<br />
## define the polarizations to show (here I use XX and YY)<br />
pol='XXYY'<br />
## The following command displays the resulting cross-power dynamic spectrum<br />
ds.plt_dspec(specfile, pol=pol) # alternatively you can use dspec as the input<br />
</pre><br />
Now you should have a popup window showing the dynamic spectrum. Hover your mouse over the dynamic spectrum, you can read the time and frequency information at the bottom of the window.<br />
<br />
===Quick-Look Imaging===<br />
Imaging EOVSA data involves image cleaning, as well as solar coordinate transformation and image registration. We bundled a number of these steps ino a module named [https://github.com/suncasa/suncasa/blob/master/utils/qlookplot.py ''qlookplot''], allowing users to generate an observing summary plot showing the cross power dynamic spectrum, GOES light curves and EOVSA quick-look images. Now let us start with making a summary plot of EOVSA image at the spectral window 5 (5.4 GHz).<br />
[[file:fig-qlookplot0.png|thumb|right|300px|EOVSA full-Sun single-band quicklook image]]<br />
<pre style="background-color: #FCEBD9"><br />
## in SunCASA<br />
from suncasa.utils import qlookplot as ql<br />
msfile = 'IDB20170821201800-202300.4s.slfcaled.ms'<br />
## (Optional) Supply the npz file of the dynamic spectrum from previous step. <br />
## If not provided, the program will generate a new one from the visibility.<br />
specfile = msfile + '.dspec.npz' <br />
## set the time interval<br />
timerange = '20:21:10~20:21:18' <br />
## select frequency range from 5 GHz to 6 GHz<br />
spw = '5~6GHz' <br />
## select stokes XX<br />
stokes = 'XX' <br />
## turn off AIA image plotting, default is True<br />
plotaia = False <br />
<br />
ql.qlookplot(vis=msfile, specfile=specfile, timerange=timerange, spw=spw, \<br />
stokes=stokes, plotaia=plotaia)<br />
</pre><br />
The empty panels are there as we only selected one polarization for imaging/spectroscopy. Feel free to explore by adjusting the above parameters, e.g. use a different time range ("timerange" parameter) and/or frequency range ("spw" parameter). <br />
<br />
With [https://github.com/suncasa/suncasa/blob/master/utils/qlookplot.py ''qlookplot''], it is easy to engage solar data from SDO/AIA in the summary plot. Setting ''plotaia=True'' in the [https://github.com/suncasa/suncasa/blob/master/utils/qlookplot.py ''qlookplot''] command will download SDO/AIA data at the given time to current directory and add it to the summary plot.<br />
[[file:fig-qlookplot1.png|thumb|right|300px|EOVSA full-Sun single-band quicklook image with SDO/AIA as background]]<br />
<pre style="background-color: #FCEBD9"><br />
## in SunCASA<br />
ql.qlookplot(vis=msfile, specfile=specfile, timerange=timerange, spw=spw, \<br />
stokes=stokes, plotaia=True)<br />
</pre><br />
The resulting radio image is a 4-D datacube (in solar X-pos, Y-pos, frequency, and polarization), which is, by default, saved as a fits file ''msfile + '.outim.image.fits''' under your working directory. The name of the output fits file can be specified using the "outfits" parameter. In this example, we combine all selected frequencies (specified in keyword "spw") into one image (i.e., multi-frequency synthesis). Therefore the third axis only has one plane. The fourth axis contains polarization. In this example, however, only the first one is populated ("XX"). Here is the relevant information in the header of the resulting FITS file.<br />
<pre> <br />
NAXIS = 4 <br />
NAXIS1 = 512/ Nx<br />
NAXIS2 = 512/ Ny <br />
NAXIS3 = 1/ number of frequency <br />
NAXIS4 = 2/ number of polarization<br />
</pre><br />
By default, [https://github.com/suncasa/suncasa/blob/master/utils/qlookplot.py ''qlookplot''] produces a full sun radio image (512x512 with a pixel size of 5"). If you know where the radio source is (e.g., from the previous full-Sun imaging), you can make a partial solar image around the source by specifying the image center ("xycen"), pixel scale ("cell"), and image field of view ("fov"). Here we show an example that images a 8-s interval around 20:21:14 UT using multi-frequency synthesis in 12-14 GHz and a smaller restoring beam. The microwave source is show to bifurcate into two components, which correspond pretty well with the double flare ribbons in SDO/AIA. <br />
[[file:fig-qlookplot3.png|thumb|right|300px|EOVSA multi-frequency synthesis quicklook image]]<br />
<pre style="background-color: #FCEBD9"><br />
## in SunCASA<br />
xycen = [375, 45] ## image center for clean in solar X-Y in arcsec<br />
cell=['2.0arcsec'] ## pixel scale<br />
imsize=[128] ## number of pixels in X and Y. If only one value is provided, NX = NY<br />
fov = [100,100] ## field of view of the zoomed-in panels in unit of arcsec<br />
ql.qlookplot(vis=msfile, specfile=specfile, timerange='20:21:10~20:21:18', \<br />
spw='12GHz~14GHz', stokes='XX', restoringbeam=['6arcsec'],\<br />
imsize=imsize,cell=cell,xycen=xycen,fov=fov,calpha=1.0)<br />
</pre><br />
<br />
Next, we will make images for every single spectral window in this data set (from spw 1 to 30, spw 0 is in the visibility data, but is not calibrated for this event). <br />
[[file:fig-qlookplot_mbds.png|thumb|right|300px|EOVSA multi-band quicklook image]]<br />
<pre style="background-color: #FCEBD9"><br />
## in SunCASA<br />
xycen = [375, 45] ## image center for clean in solar X-Y in arcsec<br />
cell=['2.0arcsec'] ## pixel size<br />
imsize=[128] ## x and y image size in pixels. <br />
fov = [100,100] ## field of view of the zoomed-in panels in unit of arcsec<br />
spw = ['{}'.format(s) for s in range(1,31)]<br />
clevels = [0.5, 1.0] ## contour levels to fill in between.<br />
calpha=0.35 ## now tune down the alpha<br />
ql.qlookplot(vis=msfile, specfile=specfile, timerange=timerange, spw=spw, stokes=stokes, \<br />
restoringbeam=restoringbeam,imsize=imsize,cell=cell, \<br />
xycen=xycen,fov=fov,clevels=clevels,calpha=calpha)<br />
</pre><br />
The output FITS file as a 4-d cube is saved to ''msfile + '.outim.image.fits''' under your working directory. The 30 spectral windows used for spectral imaging are combined in the output FITS file. So NAXIS3 (frequency axis) is 30.<br />
<pre> <br />
NAXIS = 4 / number of array dimensions <br />
NAXIS1 = 128 <br />
NAXIS2 = 128 <br />
NAXIS3 = 30 <br />
NAXIS4 = 2 <br />
</pre><br />
<br />
===Batch-Mode Imaging===<br />
This section is for interested users who wish to generate FITS files with full control on all parameters being used for synthesis imaging. We provide one example SunCASA script for generating 30-band spectral imaging maps, and another for iterating over time to produce a time series of these maps.<br />
====Producing a 30-band map cube for a given time====<br />
An example script can be found at [https://github.com/binchensun/eovsa-tutorial/blob/master/rhessi18/imaging_example.py this Github link]. If you are on the AWS server Virgo, it is under /common/data/eovsa_tutorial/imaging_example.py. First, download or copy the script to your own working directory and cd to your directory. <br />
<pre style="background-color:#FCEBD9;"><br />
# in SunCASA<br />
CASA <##>: cd your_working_directory<br />
CASA <##>: !cp /common/data/eovsa_tutorial/imaging_example.py ./<br />
</pre><br />
<br />
[[file:fig-specimg.png|thumb|right|300px|Example multi-frequency images at a single time integration]]<br />
<br />
Second (optional), change inputs in the following block in your copy of the "imaging_example.py" script and save the changes. This block has definitions for time range, image center and FOV, antennas used, cell size, number of pixels, etc.<br />
<pre><br />
################### USER INPUT GOES IN THIS BLOK ################<br />
vis = 'IDB20170821201800-202300.4s.slfcaled.ms' # input visibility data<br />
trange = '2017/08/21/20:21:00~2017/08/21/20:21:30' # time range for imaging<br />
xycen = [380., 50.] # center of the output map (in solar X and Y, Unit: arcsec)<br />
xran = [340., 420.] # plot range in solar X. Unit: arcsec<br />
yran = [10., 90.] # plot range in solar Y. Unit: arcsec<br />
antennas = '' # Use all 13 EOVSA 2-m antennas by default<br />
npix = 256 # number of pixels in the image<br />
cell = '1arcsec' # pixel scale in arcsec<br />
pol = 'XX' # polarization to image, use XX for now<br />
pbcor = True # correct for primary beam response?<br />
outdir = './images' # Specify where to save the output fits files<br />
outimgpre = 'EO' # Something to add to the output image name<br />
</pre><br />
<br />
Then, run the script in SunCASA via<br />
<pre style="background-color:#FCEBD9;"><br />
CASA <##>: execfile('imaging_example.py')<br />
</pre><br />
<br />
The output is a combined 30-band FITS file saved under "outdir". The naming conversion is outimgpre + YYYYMMDDTHHMMSS_ALLBD.fits. In this example, it is "./images/EO20170821T202115.000_ALLBD.fits". Here is the detailed information of the axes of the output FITS file.<br />
<pre> <br />
NAXIS = 4 / number of array dimensions <br />
NAXIS1 = 128 <br />
NAXIS2 = 128 <br />
NAXIS3 = 30 <br />
NAXIS4 = 2 <br />
</pre><br />
<br />
From this point, you can use your favorite language (SSWIDL users: fits2map.pro would work on these) to read the fits files and plot them. The last block of the example script uses SunPy.map to generate the plot shown on the right.<br />
<br />
====Producing a time series of 30-band maps (a 4-d cube)====<br />
An example script can be found at [https://github.com/binchensun/eovsa-tutorial/blob/master/rhessi18/imaging_timeseries_example.py this Github link]. If you are on the AWS server Virgo, it is under /common/data/eovsa_tutorial/imaging_timeseries_example.py. The script enables parallel-processing (based on a customized task "ptclean3" -- do not ask me why we have "3" in the task name). To invoke more CPU processes for parallel-processing, change "nthreads" in the preambles from 1 to the number of threads you wish to use. <br />
<br />
<span style="color:#ff0000">Caution: This script is very computationally intensive. '''Please do not try to run this script on the AWS server during the RHESSI 18 live tutorial''', as it has limited resources that everyone must share. </span><br />
<br />
<pre style="background-color:#FCEBD9;"><br />
# in SunCASA<br />
CASA <##>: cd your_working_directory<br />
CASA <##>: !cp /common/data/eovsa_tutorial/imaging_timeseries_example.py ./<br />
</pre><br />
Similar as the previous script, change inputs in the following block of your copy of the "imaging_timeseries_example.py" script and save the changes. <br />
<br />
[[file:fig-specmovie.png|thumb|right|300px|Example multi-frequency images at one time frame in the [https://web.njit.edu/~sjyu/download/eovsa-tutorial/movie.html output javascript movie]]]<br />
<pre><br />
################### USER INPUT GOES IN THIS BLOK ####################<br />
vis = 'IDB20170821201800-202300.4s.slfcaled.ms' # input visibility data<br />
specfile = vis + '.dspec.npz' ## input dynamic spectrum<br />
nthreads = 1 # Number of processing threads to use<br />
overwrite = True # whether to overwrite the existed fits files.<br />
trange = '' # time range for imaging, default to all times in the data<br />
twidth = 1 # make one image out of every 2 time integrations<br />
xycen = [380., 50.] # center of the output map in solar X and Y. Unit: arcsec<br />
xran = [340., 420.] # plot range in solar X. Unit: arcsec<br />
yran = [10., 90.] # plot range in solar Y. Unit: arcsec<br />
antennas = '' # default is to use all 13 EOVSA 2-m antennas. <br />
npix = 128 # number of pixels in the image<br />
cell = '2arcsec' # pixel scale in arcsec<br />
pol = 'XX' # polarization to image, use XX for now<br />
pbcor = True # correct for primary beam response?<br />
grid_spacing = 5. * u.deg # grid spacing in degrees<br />
outdir = './image_series/' # Specify where to save the output fits files<br />
imresfile = 'imres.npz' # File to write summary of the imaging results<br />
outimgpre = 'EO' # Something to add to the image name<br />
</pre><br />
<br />
Then, run the script in SunCASA by<br />
<pre style="background-color:#FCEBD9;"><br />
CASA <##>: execfile('imaging_timeseries_example.py')<br />
</pre><br />
<br />
The output fits images and a summary file imresfile are saved under "outdir" (in this example "./image_timeseries"). The naming convention of output fits images is the same as [[#Producing a 30-band map at a given time|the previous section]]. The summary yields the time, frequency, and path to every image.<br />
<pre style="background-color:#FCEBD9;"><br />
CASA <##>: imres = np.load(outdir + imresfile)['imres'].item()<br />
CASA <##>: imres.keys()<br />
['FreqGHz', 'ImageName', 'Succeeded', 'BeginTime', 'EndTime']<br />
CASA <##>: ls image_series/*.fits | head -5<br />
image_series/EO20170821T201800.500_ALLBD.fits<br />
image_series/EO20170821T201804.500_ALLBD.fits<br />
image_series/EO20170821T201808.500_ALLBD.fits<br />
image_series/EO20170821T201812.500_ALLBD.fits<br />
image_series/EO20170821T201816.500_ALLBD.fits<br />
</pre><br />
The last block of the example script uses SunPy.map to generate a series of plots and wraps them as a [https://web.njit.edu/~sjyu/download/eovsa-tutorial/movie.html javascript movie].<br />
<br />
====Plotting Images in SSWIDL====<br />
All the output files are in standard FITS format in the Helioprojective Cartesian coordinate system (that most spacecraft solar image data adopt; FITS header CTYPE is HPLN-TAN and HPLT-TAN). They are fully compatible with [https://hesperia.gsfc.nasa.gov/rhessidatacenter/complementary_data/maps/ the SSWIDL map suite] which deals with FITS files. We have prepared SSWIDL routines to convert the single time or time-series FITS files to an array of SSWIDL map structure. The scripts are available in the [https://github.com/binchensun/eovsa-tutorial/tree/master/rhessi18 Github repository of our tutorial]. For those working on Virgo, local copies are placed under /common/data/eovsa_tutorial/. Two scripts are relevant to this tutorial:<br />
* [https://github.com/binchensun/eovsa-tutorial/blob/master/rhessi18/casa_readfits.pro casa_readfits.pro]: read an array of multi-frequency FITS files into FITS header (index) and data.<br />
* [https://github.com/binchensun/eovsa-tutorial/blob/master/rhessi18/casa_fits2map.pro casa_fits2map.pro]: convert an array of multi-frequency FITS files into an array of SSWIDL map structure (adapted from P. T. Gallagher's hsi_fits2map.pro)<br />
<br />
First, start SSWIDL from command line:<br />
<pre style="background-color:#FCEBD9;"><br />
sswidl<br />
</pre><br />
<br />
Find and convert the fits files:<br />
<pre style="background-color:#FCEBD9;"><br />
; cd to your path that contains casa_readfits.pro and casa_fits2map.pro. If on Virgo, just add the path<br />
IDL> add_path, '/common/data/eovsa_tutorial/'<br />
IDL> fitsdir = '/common/data/eovsa_tutorial/image_series/'<br />
IDL> fitsfiles = file_search(fitsdir+'*_ALLBD.fits')<br />
; The resulting fitfiles contains all multi-frequency FITS files under "fitsdir" <br />
; The following command converts the fits files to an array of map structures. <br />
; "casa_fits2map.pro" also work well on a single FITS file. <br />
; (Optional) keyword "calcrms" is to calculate rms and dynamic range (SNR) of the maps in a user-defined "empty" region <br />
; of the map specified by "rmsxran" and "rmsyran"<br />
IDL> casa_fits2map, fitsfiles, eomaps[, /calcrms, rmsxran=[260., 320.], rmsyran=[-70., 0.]]<br />
; Save the output maps as an IDL save file for future use<br />
IDL> save,file='EOMAPS_20170821T201800-202300.4s.sav',eomaps<br />
</pre><br />
<br />
The resulting maps have a shape of [# of frequencies, # of polarizations, # of times]<br />
<pre style="background-color:#FCEBD9;"><br />
IDL> help,eomaps<br />
EOMAPS STRUCT = -> <Anonymous> Array[30, 1, 75]<br />
</pre><br />
They have compatible keywords recognized by, e.g., plot_map.pro. Example of the output map keywords:<br />
<pre style="background-color:#FCEBD9;"><br />
IDL> help,eomaps,/str <br />
** Structure <3bcf8e8>, 29 tags, length=131384, data length=131380, refs=1:<br />
DATA DOUBLE Array[128, 128]<br />
XC DOUBLE 378.99123<br />
YC DOUBLE 49.005429<br />
DX DOUBLE 2.0000000<br />
DY DOUBLE 2.0000000<br />
TIME STRING '21-Aug-2017 20:18:00.500'<br />
ID STRING 'EOVSA XX 3.413GHz'<br />
DUR DOUBLE 4.0000003<br />
XUNITS STRING 'arcsec'<br />
YUNITS STRING 'arcsec'<br />
ROLL_ANGLE DOUBLE 0.0000000<br />
ROLL_CENTER DOUBLE Array[2]<br />
FREQ DOUBLE 3.4125694<br />
FREQUNIT STRING 'GHz'<br />
STOKES STRING 'XX'<br />
DATAUNIT STRING 'K'<br />
DATATYPE STRING 'Brightness Temperature'<br />
BMAJ DOUBLE 0.0097377778<br />
BMIN DOUBLE 0.0097377778<br />
BPA DOUBLE 0.0000000<br />
RSUN DOUBLE 948.03949<br />
L0 FLOAT 0.00000<br />
B0 DOUBLE 6.9298481<br />
COMMENT STRING 'Converted by CASA_FITS2MAP.PRO'<br />
RMS DOUBLE 22995.481<br />
SNR DOUBLE 92.201139<br />
RMSUNIT STRING 'K'<br />
RMSXRAN FLOAT Array[2]<br />
RMSYRAN FLOAT Array[2]<br />
</pre><br />
<br />
[[file:fig-specimg_idl.png|thumb|right|300px|Example multi-frequency EOVSA images at one time plotted in SSWIDL]]<br />
An example for plotting all images at a selected time:<br />
<pre style="background-color:#FCEBD9;"><br />
; choose a time pixel<br />
IDL> plttime = anytim('2017-08-21T20:21:15')<br />
IDL> dt = min(abs(anytim(eomaps[0,0,*].time)-plttime),tidx)<br />
; use maps at this time, first polarization, and all bands<br />
IDL> eomap = reform(eomaps[*,0,tidx])<br />
IDL> window,0,xs=1000,ys=800<br />
IDL> !p.multi=[0,6,5]<br />
IDL> loadct, 3<br />
IDL> for i=0, 29 do plot_map,eomap[i],grid=5.,$<br />
tit=string(eomap[i].freq,format='(f5.2)')+' GHz', $<br />
chars=2.0,xran=[340.,420.],yran=[10.,90.]<br />
</pre><br />
<br />
==Spectral Fitting with GSFIT==<br />
In this section we discuss using GSFIT (now a package of SSWIDL) to perform spectral fit based on the resulting FITS images produced from the previous steps. We will use the IDL save file produced in [[#Plotting Images in SSWIDL|Section 3.3.3.3]] as the input. A copy of the IDL save file can be downloaded from this link. On Virgo, the IDL save file is located at /common/data/eovsa_tutorial/21August2017.sav. In addition, this folder contains three more demo files that may be used to demonstrate the GSFIT functionality. <br />
For those intending to use their own machines for this part of the tutorial, these IDL fits files may be downloaded from [https://www.dropbox.com/sh/tjez92wfph1jp7x/AAAJBO6AJ0GC5H3GCZypc2BYa?dl=0 this location]<br />
<br />
<br />
===GSFIT GUI Application===<br />
The GSFIT GUI application may be launched as follows<br />
<br />
<pre><br />
IDL> gsfit [,nthreads]<br />
</pre><br />
<br />
where '''nthreads''' is an optional argument that indicates the number of parallel asynchronous threads to be used when performing the fit tasks. By default, GSFIT launches with only one thread, but the user may interactively add or delete threads as needed at the run-time up to the number of CPUs available on the system (<b>Note, if you are working on the AWS server, please use only one thread</b>). After some delay while the interface loads, the GUI below should appear.<br />
<br />
<gallery widths=600px heights=300px><br />
File:GSFITwin.png|GSFIT GUI appearance on Windows OS<br />
File:GSFITunix.png|GSFIT GUI appearance on Linux/Mac OS<br />
</gallery><br />
<br />
A detailed description of the GSFIT functionality is provided in the page linked below. <br />
====[[GSFIT Help]]====<br />
<br />
===GSFITCP Batch Mode Application===<br />
GSFITCP is the command prompt counterpart of the GSFIT GUI microwave spectral fitting application. Once started, GSFITCP is designed to run in unattended mode until all fitting tasks assigned to it are completed and log on the disk in an user-defined *.log file, the content of which may be visualized using the GSFITVIEW GUI application. When run remotely on an Linux/Mac platform, the GSFITCP may be launched on a detached [https://linuxize.com/post/how-to-use-linux-screen/ screen], which allows the remote user to logout without stopping the process in which GSFITCP runs.<br />
<br />
GSFITCP is launched using the following call:<br />
<pre><br />
IDL> gsfitcp, taskfile, nthreads, /start<br />
</pre><br />
where '''''taskfile''''' is a path to a file in which a GSFIT task has been previously saved, as explained in the [[GSFIT Help]] page, '''''nthreads''''' is an optional argument indicating the number of parallel asynchronous threads to be used, and the optional keyword '''''/start''''', if set, requests immediate start of the batch processing. <br />
<br />
A detailed description of the GSFITCP functionality is provided in the page linked below. <br />
====[[GSFITCP Help]]====<br />
<br />
===GSFITVIEW GUI Application===<br />
The GSFITVIEW GUI application may be launched as follows<br />
<pre><br />
IDL> gsfitview [,gsfitmaps]<br />
</pre><br />
where the optional '''gsfitmaps''' argument is either the filename of an IDL ''*.sav'' file containg a GSFIT Parameter Map Cube structure produced by the GSFIT or GSFITCP applications, or an already restored such structure.<br />
<gallery widths=600px heights=400px><br />
File:GSFITVIEWwin.png<br />
File:GSFITVIEWunix.png<br />
]</gallery><br />
<br />
<br />
A detailed description of the GSFITVIEW functionality is provided in the page linked below. <br />
====[[GSFITVIEW Help]]====<br />
<br />
===[[GSFIT Data Format]]===</div>Gnitahttp://ovsa.njit.edu//wiki/index.php?title=GSFIT_Installation&diff=4450GSFIT Installation2019-05-27T11:58:17Z<p>Gnita: /* GSFIT SSW_UPGRADE Installation */</p>
<hr />
<div>[https://github.com/Gelu-Nita/GSFIT GSFIT] is an IDL-widget(GUI)-based spectral fitting package that provides a user-friendly display of [http://www.ovsa.njit.edu/ EOVSA] image cubes and an interface to fast fitting codes (via platform-dependent shared-object libraries). Fits to individual spectra can be done quickly for manual investigation using a GUI application called [http://www.ovsa.njit.edu/wiki/index.php/GSFIT_Help GSFIT], while parallel/multi-core batch processing of selected blocks of data can also be performed using a command prompt application called [http://www.ovsa.njit.edu/wiki/index.php/GSFITCP_Help GSFITCP]. A helper routine called [http://www.ovsa.njit.edu/wiki/index.php/GSFITVIEW_Help GSFITVIEW] allows further display and investigation of the fitting results.<br />
For detailed information about these applications, please visit the pages linked below.<br />
*[[GSFIT Help]]<br />
*[[GSFITCP Help]]<br />
*[[GSFITVIEW Help]]<br />
<br />
Platform specific installation instructions for the GSFIT package are provided on this page.<br />
<br />
=GSFIT IDL Version Requirements (All Platforms)= <br />
<span style="color:red">'''IDL8.4, or higher, is needed for running any of the applications included in this package'''</span>.<br />
<br />
=GSFIT Linux / Mac OS Requirements=<br />
On Mac and Unix platforms, the gfortran compiler must be also installed to allow automatic compilation of the source code located in the ..//gsfit/unix directory, in order to generate a series of shared libraries, when gsfit is launched for the first time. WARNING: For this action to be successfully completed, the user must have writing rights to the ..//gsfit/unix directory.<br />
<br />
'''If needed, instructions for installing the gfortran compiler may be found [http://www.lapk.org/gfortran/gfortran.php?OS=7 here].'''<br />
<br />
=GSFIT Windows OS Requirements=<br />
The GSFIT package is distributed along with a set of dynamic link libraries located in the ..//gsfit/win subfolder, which have been compiled assuming a WIN64 architecture. For Win32, please contact us to inquire about alternative options.<br />
<br />
=GSFIT SSW_UPGRADE Installation=<br />
The release version of the IDL GSFIT package is intended to be distributed through the [https://www.lmsal.com/solarsoft/ SSW IDL repository]. <br />
Although installed as a stand-alone package, the GSFIT code relies on a series of IDL support routines that are part of the gx_simulator package. Therefore, in addition to installing the gsfit package , the gx_simulator package must be also installed. This installation can be performed by issuing an upgrade command, i.e.<br />
<br />
<pre><br />
IDL> ssw_upgrade,/gsfit,/gx_simulator,/gen,/spawn,/loud,/passive_ftp <br />
</pre><br />
<br />
=GSFIT SSW Instrument Setup=<br />
After the SSW installation is upgraded to include gsfit and gx_simulator packages, to ensure proper functionality, one should also edit the sswidl.bat (on Windows platforms) or cshrc (on Unix or Mac platforms) scripts to include gx_simulator and gsfit in the SSW_INSTR path declaration, i.e.<br />
<pre><br />
set SSW_INSTR=gx_simulator, gsfit [...] <br />
</pre><br />
where [..] denotes any other SSW packages already installed.<br />
<br />
=GSFIT Manual Stand-Alone Installation=<br />
Although '''not reccomended''', one may in principle choose to install the gsfit and gx_simulator packages in standalone directories that are not part of the SSW repositories. However if this (not recommended) option is used, the gsfit and gx_simulator paths should be explicitly added to the IDL !path global variable, i.e. <br />
<br />
and explicitly add this path to your IDL path structure.<br />
<br />
<pre><br />
IDL> !path='..//gsfit/idl:'+!path<br />
IDL> !path='..//gx_simulator/idl:'+!path<br />
</pre><br />
<br />
where '''../''' should be replaced with the explicit paths to the respective local machine repositories.</div>Gnitahttp://ovsa.njit.edu//wiki/index.php?title=GSFIT_Installation&diff=4449GSFIT Installation2019-05-27T11:57:34Z<p>Gnita: /* GSFIT Linux / Mac OS Requirements */</p>
<hr />
<div>[https://github.com/Gelu-Nita/GSFIT GSFIT] is an IDL-widget(GUI)-based spectral fitting package that provides a user-friendly display of [http://www.ovsa.njit.edu/ EOVSA] image cubes and an interface to fast fitting codes (via platform-dependent shared-object libraries). Fits to individual spectra can be done quickly for manual investigation using a GUI application called [http://www.ovsa.njit.edu/wiki/index.php/GSFIT_Help GSFIT], while parallel/multi-core batch processing of selected blocks of data can also be performed using a command prompt application called [http://www.ovsa.njit.edu/wiki/index.php/GSFITCP_Help GSFITCP]. A helper routine called [http://www.ovsa.njit.edu/wiki/index.php/GSFITVIEW_Help GSFITVIEW] allows further display and investigation of the fitting results.<br />
For detailed information about these applications, please visit the pages linked below.<br />
*[[GSFIT Help]]<br />
*[[GSFITCP Help]]<br />
*[[GSFITVIEW Help]]<br />
<br />
Platform specific installation instructions for the GSFIT package are provided on this page.<br />
<br />
=GSFIT IDL Version Requirements (All Platforms)= <br />
<span style="color:red">'''IDL8.4, or higher, is needed for running any of the applications included in this package'''</span>.<br />
<br />
=GSFIT Linux / Mac OS Requirements=<br />
On Mac and Unix platforms, the gfortran compiler must be also installed to allow automatic compilation of the source code located in the ..//gsfit/unix directory, in order to generate a series of shared libraries, when gsfit is launched for the first time. WARNING: For this action to be successfully completed, the user must have writing rights to the ..//gsfit/unix directory.<br />
<br />
'''If needed, instructions for installing the gfortran compiler may be found [http://www.lapk.org/gfortran/gfortran.php?OS=7 here].'''<br />
<br />
=GSFIT Windows OS Requirements=<br />
The GSFIT package is distributed along with a set of dynamic link libraries located in the ..//gsfit/win subfolder, which have been compiled assuming a WIN64 architecture. For Win32, please contact us to inquire about alternative options.<br />
<br />
=GSFIT SSW_UPGRADE Installation=<br />
The release version of the IDL GSFIT package is intended to be distributed through the SSW IDL repository [https://www.lmsal.com/solarsoft/]. <br />
Although installed as a stand-alone package, the GSFIT code relies on a series of IDL support routines that are part of the gx_simulator package. Therefore, in addition to installing the gsfit package , the gx_simulator package must be also installed. This installation can be performed by issuing an upgrade command, i.e.<br />
<br />
<pre><br />
IDL> ssw_upgrade,/gsfit,/gx_simulator,/gen,/spawn,/loud,/passive_ftp <br />
</pre><br />
<br />
=GSFIT SSW Instrument Setup=<br />
After the SSW installation is upgraded to include gsfit and gx_simulator packages, to ensure proper functionality, one should also edit the sswidl.bat (on Windows platforms) or cshrc (on Unix or Mac platforms) scripts to include gx_simulator and gsfit in the SSW_INSTR path declaration, i.e.<br />
<pre><br />
set SSW_INSTR=gx_simulator, gsfit [...] <br />
</pre><br />
where [..] denotes any other SSW packages already installed.<br />
<br />
=GSFIT Manual Stand-Alone Installation=<br />
Although '''not reccomended''', one may in principle choose to install the gsfit and gx_simulator packages in standalone directories that are not part of the SSW repositories. However if this (not recommended) option is used, the gsfit and gx_simulator paths should be explicitly added to the IDL !path global variable, i.e. <br />
<br />
and explicitly add this path to your IDL path structure.<br />
<br />
<pre><br />
IDL> !path='..//gsfit/idl:'+!path<br />
IDL> !path='..//gx_simulator/idl:'+!path<br />
</pre><br />
<br />
where '''../''' should be replaced with the explicit paths to the respective local machine repositories.</div>Gnitahttp://ovsa.njit.edu//wiki/index.php?title=GSFIT_Installation&diff=4448GSFIT Installation2019-05-27T11:54:02Z<p>Gnita: /* GSFIT IDL Version Requirements (All Platforms) */</p>
<hr />
<div>[https://github.com/Gelu-Nita/GSFIT GSFIT] is an IDL-widget(GUI)-based spectral fitting package that provides a user-friendly display of [http://www.ovsa.njit.edu/ EOVSA] image cubes and an interface to fast fitting codes (via platform-dependent shared-object libraries). Fits to individual spectra can be done quickly for manual investigation using a GUI application called [http://www.ovsa.njit.edu/wiki/index.php/GSFIT_Help GSFIT], while parallel/multi-core batch processing of selected blocks of data can also be performed using a command prompt application called [http://www.ovsa.njit.edu/wiki/index.php/GSFITCP_Help GSFITCP]. A helper routine called [http://www.ovsa.njit.edu/wiki/index.php/GSFITVIEW_Help GSFITVIEW] allows further display and investigation of the fitting results.<br />
For detailed information about these applications, please visit the pages linked below.<br />
*[[GSFIT Help]]<br />
*[[GSFITCP Help]]<br />
*[[GSFITVIEW Help]]<br />
<br />
Platform specific installation instructions for the GSFIT package are provided on this page.<br />
<br />
=GSFIT IDL Version Requirements (All Platforms)= <br />
<span style="color:red">'''IDL8.4, or higher, is needed for running any of the applications included in this package'''</span>.<br />
<br />
=GSFIT Linux / Mac OS Requirements=<br />
On Mac and Unix platforms, the gfortran compiler must be also installed to allow automatic compilation of the source code located in the ..//gsfit/unix directory, in order to generate a series of shared libraries, when gsfit is launched for the first time. WARNING: For this action to be successfully completed, the user must have writing rights to the ..//gsfit/unix directory.<br />
<br />
'''Instructions for installing the gfortran compiler, if missing, may be found [http://www.lapk.org/gfortran/gfortran.php?OS=7 here].'''<br />
<br />
=GSFIT Windows OS Requirements=<br />
The GSFIT package is distributed along with a set of dynamic link libraries located in the ..//gsfit/win subfolder, which have been compiled assuming a WIN64 architecture. For Win32, please contact us to inquire about alternative options.<br />
<br />
=GSFIT SSW_UPGRADE Installation=<br />
The release version of the IDL GSFIT package is intended to be distributed through the SSW IDL repository [https://www.lmsal.com/solarsoft/]. <br />
Although installed as a stand-alone package, the GSFIT code relies on a series of IDL support routines that are part of the gx_simulator package. Therefore, in addition to installing the gsfit package , the gx_simulator package must be also installed. This installation can be performed by issuing an upgrade command, i.e.<br />
<br />
<pre><br />
IDL> ssw_upgrade,/gsfit,/gx_simulator,/gen,/spawn,/loud,/passive_ftp <br />
</pre><br />
<br />
=GSFIT SSW Instrument Setup=<br />
After the SSW installation is upgraded to include gsfit and gx_simulator packages, to ensure proper functionality, one should also edit the sswidl.bat (on Windows platforms) or cshrc (on Unix or Mac platforms) scripts to include gx_simulator and gsfit in the SSW_INSTR path declaration, i.e.<br />
<pre><br />
set SSW_INSTR=gx_simulator, gsfit [...] <br />
</pre><br />
where [..] denotes any other SSW packages already installed.<br />
<br />
=GSFIT Manual Stand-Alone Installation=<br />
Although '''not reccomended''', one may in principle choose to install the gsfit and gx_simulator packages in standalone directories that are not part of the SSW repositories. However if this (not recommended) option is used, the gsfit and gx_simulator paths should be explicitly added to the IDL !path global variable, i.e. <br />
<br />
and explicitly add this path to your IDL path structure.<br />
<br />
<pre><br />
IDL> !path='..//gsfit/idl:'+!path<br />
IDL> !path='..//gx_simulator/idl:'+!path<br />
</pre><br />
<br />
where '''../''' should be replaced with the explicit paths to the respective local machine repositories.</div>Gnitahttp://ovsa.njit.edu//wiki/index.php?title=GSFIT_Installation&diff=4447GSFIT Installation2019-05-27T11:53:35Z<p>Gnita: /* GSFIT IDL Version Requirements (All Platforms) */</p>
<hr />
<div>[https://github.com/Gelu-Nita/GSFIT GSFIT] is an IDL-widget(GUI)-based spectral fitting package that provides a user-friendly display of [http://www.ovsa.njit.edu/ EOVSA] image cubes and an interface to fast fitting codes (via platform-dependent shared-object libraries). Fits to individual spectra can be done quickly for manual investigation using a GUI application called [http://www.ovsa.njit.edu/wiki/index.php/GSFIT_Help GSFIT], while parallel/multi-core batch processing of selected blocks of data can also be performed using a command prompt application called [http://www.ovsa.njit.edu/wiki/index.php/GSFITCP_Help GSFITCP]. A helper routine called [http://www.ovsa.njit.edu/wiki/index.php/GSFITVIEW_Help GSFITVIEW] allows further display and investigation of the fitting results.<br />
For detailed information about these applications, please visit the pages linked below.<br />
*[[GSFIT Help]]<br />
*[[GSFITCP Help]]<br />
*[[GSFITVIEW Help]]<br />
<br />
Platform specific installation instructions for the GSFIT package are provided on this page.<br />
<br />
=GSFIT IDL Version Requirements (All Platforms)= <br />
<span style="color:red">'''IDL8.4, or a higher version, is needed for running any of the applications included in this package'''</span>.<br />
<br />
=GSFIT Linux / Mac OS Requirements=<br />
On Mac and Unix platforms, the gfortran compiler must be also installed to allow automatic compilation of the source code located in the ..//gsfit/unix directory, in order to generate a series of shared libraries, when gsfit is launched for the first time. WARNING: For this action to be successfully completed, the user must have writing rights to the ..//gsfit/unix directory.<br />
<br />
'''Instructions for installing the gfortran compiler, if missing, may be found [http://www.lapk.org/gfortran/gfortran.php?OS=7 here].'''<br />
<br />
=GSFIT Windows OS Requirements=<br />
The GSFIT package is distributed along with a set of dynamic link libraries located in the ..//gsfit/win subfolder, which have been compiled assuming a WIN64 architecture. For Win32, please contact us to inquire about alternative options.<br />
<br />
=GSFIT SSW_UPGRADE Installation=<br />
The release version of the IDL GSFIT package is intended to be distributed through the SSW IDL repository [https://www.lmsal.com/solarsoft/]. <br />
Although installed as a stand-alone package, the GSFIT code relies on a series of IDL support routines that are part of the gx_simulator package. Therefore, in addition to installing the gsfit package , the gx_simulator package must be also installed. This installation can be performed by issuing an upgrade command, i.e.<br />
<br />
<pre><br />
IDL> ssw_upgrade,/gsfit,/gx_simulator,/gen,/spawn,/loud,/passive_ftp <br />
</pre><br />
<br />
=GSFIT SSW Instrument Setup=<br />
After the SSW installation is upgraded to include gsfit and gx_simulator packages, to ensure proper functionality, one should also edit the sswidl.bat (on Windows platforms) or cshrc (on Unix or Mac platforms) scripts to include gx_simulator and gsfit in the SSW_INSTR path declaration, i.e.<br />
<pre><br />
set SSW_INSTR=gx_simulator, gsfit [...] <br />
</pre><br />
where [..] denotes any other SSW packages already installed.<br />
<br />
=GSFIT Manual Stand-Alone Installation=<br />
Although '''not reccomended''', one may in principle choose to install the gsfit and gx_simulator packages in standalone directories that are not part of the SSW repositories. However if this (not recommended) option is used, the gsfit and gx_simulator paths should be explicitly added to the IDL !path global variable, i.e. <br />
<br />
and explicitly add this path to your IDL path structure.<br />
<br />
<pre><br />
IDL> !path='..//gsfit/idl:'+!path<br />
IDL> !path='..//gx_simulator/idl:'+!path<br />
</pre><br />
<br />
where '''../''' should be replaced with the explicit paths to the respective local machine repositories.</div>Gnitahttp://ovsa.njit.edu//wiki/index.php?title=GSFIT_Installation&diff=4446GSFIT Installation2019-05-27T11:52:44Z<p>Gnita: </p>
<hr />
<div>[https://github.com/Gelu-Nita/GSFIT GSFIT] is an IDL-widget(GUI)-based spectral fitting package that provides a user-friendly display of [http://www.ovsa.njit.edu/ EOVSA] image cubes and an interface to fast fitting codes (via platform-dependent shared-object libraries). Fits to individual spectra can be done quickly for manual investigation using a GUI application called [http://www.ovsa.njit.edu/wiki/index.php/GSFIT_Help GSFIT], while parallel/multi-core batch processing of selected blocks of data can also be performed using a command prompt application called [http://www.ovsa.njit.edu/wiki/index.php/GSFITCP_Help GSFITCP]. A helper routine called [http://www.ovsa.njit.edu/wiki/index.php/GSFITVIEW_Help GSFITVIEW] allows further display and investigation of the fitting results.<br />
For detailed information about these applications, please visit the pages linked below.<br />
*[[GSFIT Help]]<br />
*[[GSFITCP Help]]<br />
*[[GSFITVIEW Help]]<br />
<br />
Platform specific installation instructions for the GSFIT package are provided on this page.<br />
<br />
=GSFIT IDL Version Requirements (All Platforms)= <br />
<span style="color:red">'''An IDL8.4 version, or higher, is needed for running any of the applications included in this package'''</span>.<br />
=GSFIT Linux / Mac OS Requirements=<br />
On Mac and Unix platforms, the gfortran compiler must be also installed to allow automatic compilation of the source code located in the ..//gsfit/unix directory, in order to generate a series of shared libraries, when gsfit is launched for the first time. WARNING: For this action to be successfully completed, the user must have writing rights to the ..//gsfit/unix directory.<br />
<br />
'''Instructions for installing the gfortran compiler, if missing, may be found [http://www.lapk.org/gfortran/gfortran.php?OS=7 here].'''<br />
<br />
=GSFIT Windows OS Requirements=<br />
The GSFIT package is distributed along with a set of dynamic link libraries located in the ..//gsfit/win subfolder, which have been compiled assuming a WIN64 architecture. For Win32, please contact us to inquire about alternative options.<br />
<br />
=GSFIT SSW_UPGRADE Installation=<br />
The release version of the IDL GSFIT package is intended to be distributed through the SSW IDL repository [https://www.lmsal.com/solarsoft/]. <br />
Although installed as a stand-alone package, the GSFIT code relies on a series of IDL support routines that are part of the gx_simulator package. Therefore, in addition to installing the gsfit package , the gx_simulator package must be also installed. This installation can be performed by issuing an upgrade command, i.e.<br />
<br />
<pre><br />
IDL> ssw_upgrade,/gsfit,/gx_simulator,/gen,/spawn,/loud,/passive_ftp <br />
</pre><br />
<br />
=GSFIT SSW Instrument Setup=<br />
After the SSW installation is upgraded to include gsfit and gx_simulator packages, to ensure proper functionality, one should also edit the sswidl.bat (on Windows platforms) or cshrc (on Unix or Mac platforms) scripts to include gx_simulator and gsfit in the SSW_INSTR path declaration, i.e.<br />
<pre><br />
set SSW_INSTR=gx_simulator, gsfit [...] <br />
</pre><br />
where [..] denotes any other SSW packages already installed.<br />
<br />
=GSFIT Manual Stand-Alone Installation=<br />
Although '''not reccomended''', one may in principle choose to install the gsfit and gx_simulator packages in standalone directories that are not part of the SSW repositories. However if this (not recommended) option is used, the gsfit and gx_simulator paths should be explicitly added to the IDL !path global variable, i.e. <br />
<br />
and explicitly add this path to your IDL path structure.<br />
<br />
<pre><br />
IDL> !path='..//gsfit/idl:'+!path<br />
IDL> !path='..//gx_simulator/idl:'+!path<br />
</pre><br />
<br />
where '''../''' should be replaced with the explicit paths to the respective local machine repositories.</div>Gnitahttp://ovsa.njit.edu//wiki/index.php?title=GSFIT_Installation&diff=4445GSFIT Installation2019-05-27T11:52:18Z<p>Gnita: /* GSFIT IDL Version Requirements(All Platforms) */</p>
<hr />
<div>[https://github.com/Gelu-Nita/GSFIT GSFIT] is an IDL-widget(GUI)-based spectral fitting package that provides a user-friendly display of [http://www.ovsa.njit.edu/ EOVSA] image cubes and an interface to fast fitting codes (via platform-dependent shared-object libraries). Fits to individual spectra can be done quickly for manual investigation using a GUI application called [http://www.ovsa.njit.edu/wiki/index.php/GSFIT_Help GSFIT], while parallel/multi-core batch processing of selected blocks of data can also be performed using a command prompt application called [http://www.ovsa.njit.edu/wiki/index.php/GSFITCP_Help GSFITCP]. A helper routine called [http://www.ovsa.njit.edu/wiki/index.php/GSFITVIEW_Help GSFITVIEW] allows further display and investigation of the fitting results.<br />
For detailed information about these applications, please visit the pages linked below.<br />
*[[GSFIT Help]]<br />
*[[GSFITCP Help]]<br />
*[[GSFITVIEW Help]]<br />
<br />
Platform specific installation instructions for the GSFIT package are provided on this page.<br />
<br />
=GSFIT IDL Version Requirements (All Platforms)= <br />
<span style="color:red">'''An IDL8.4 version, or higher, is needed for running any of the applications included in this package'''</span>.<br />
<br />
=GSFIT Linux / Mac OS Requirements=<br />
On Mac and Unix platforms, the gfortran compiler must be also installed to allow automatic compilation of the source code located in the ..//gsfit/unix directory, in order to generate a series of shared libraries, when gsfit is launched for the first time. WARNING: For this action to be successfully completed, the user must have writing rights to the ..//gsfit/unix directory.<br />
<br />
'''Instructions for installing the gfortran compiler, if missing, may be found [http://www.lapk.org/gfortran/gfortran.php?OS=7 here].'''<br />
<br />
=GSFIT Windows OS Requirements=<br />
The GSFIT package is distributed along with a set of dynamic link libraries located in the ..//gsfit/win subfolder, which have been compiled assuming a WIN64 architecture. For Win32, please contact us to inquire about alternative options.<br />
<br />
=GSFIT SSW_UPGRADE Installation=<br />
The release version of the IDL GSFIT package is intended to be distributed through the SSW IDL repository [https://www.lmsal.com/solarsoft/]. <br />
Although installed as a stand-alone package, the GSFIT code relies on a series of IDL support routines that are part of the gx_simulator package. Therefore, in addition to installing the gsfit package , the gx_simulator package must be also installed. This installation can be performed by issuing an upgrade command, i.e.<br />
<br />
<pre><br />
IDL> ssw_upgrade,/gsfit,/gx_simulator,/gen,/spawn,/loud,/passive_ftp <br />
</pre><br />
<br />
=GSFIT SSW Instrument Setup=<br />
After the SSW installation is upgraded to include gsfit and gx_simulator packages, to ensure proper functionality, one should also edit the sswidl.bat (on Windows platforms) or cshrc (on Unix or Mac platforms) scripts to include gx_simulator and gsfit in the SSW_INSTR path declaration, i.e.<br />
<pre><br />
set SSW_INSTR=gx_simulator, gsfit [...] <br />
</pre><br />
where [..] denotes any other SSW packages already installed.<br />
<br />
=GSFIT Manual Stand-Alone Installation=<br />
Although '''not reccomended''', one may in principle choose to install the gsfit and gx_simulator packages in standalone directories that are not part of the SSW repositories. However if this (not recommended) option is used, the gsfit and gx_simulator paths should be explicitly added to the IDL !path global variable, i.e. <br />
<br />
and explicitly add this path to your IDL path structure.<br />
<br />
<pre><br />
IDL> !path='..//gsfit/idl:'+!path<br />
IDL> !path='..//gx_simulator/idl:'+!path<br />
</pre><br />
<br />
where '''../''' should be replaced with the explicit paths to the respective local machine repositories.</div>Gnitahttp://ovsa.njit.edu//wiki/index.php?title=GSFIT_Installation&diff=4444GSFIT Installation2019-05-27T11:51:30Z<p>Gnita: /* GSFIT IDL Version Requirements(All Platforms) */</p>
<hr />
<div>[https://github.com/Gelu-Nita/GSFIT GSFIT] is an IDL-widget(GUI)-based spectral fitting package that provides a user-friendly display of [http://www.ovsa.njit.edu/ EOVSA] image cubes and an interface to fast fitting codes (via platform-dependent shared-object libraries). Fits to individual spectra can be done quickly for manual investigation using a GUI application called [http://www.ovsa.njit.edu/wiki/index.php/GSFIT_Help GSFIT], while parallel/multi-core batch processing of selected blocks of data can also be performed using a command prompt application called [http://www.ovsa.njit.edu/wiki/index.php/GSFITCP_Help GSFITCP]. A helper routine called [http://www.ovsa.njit.edu/wiki/index.php/GSFITVIEW_Help GSFITVIEW] allows further display and investigation of the fitting results.<br />
For detailed information about these applications, please visit the pages linked below.<br />
*[[GSFIT Help]]<br />
*[[GSFITCP Help]]<br />
*[[GSFITVIEW Help]]<br />
<br />
Platform specific installation instructions for the GSFIT package are provided on this page.<br />
<br />
=GSFIT IDL Version Requirements(All Platforms)= <br />
<span style="color:red">'''An IDL8.4 version, or higher, is needed for running any of the applications included in this package'''</span>.<br />
<br />
=GSFIT Linux / Mac OS Requirements=<br />
On Mac and Unix platforms, the gfortran compiler must be also installed to allow automatic compilation of the source code located in the ..//gsfit/unix directory, in order to generate a series of shared libraries, when gsfit is launched for the first time. WARNING: For this action to be successfully completed, the user must have writing rights to the ..//gsfit/unix directory.<br />
<br />
'''Instructions for installing the gfortran compiler, if missing, may be found [http://www.lapk.org/gfortran/gfortran.php?OS=7 here].'''<br />
<br />
=GSFIT Windows OS Requirements=<br />
The GSFIT package is distributed along with a set of dynamic link libraries located in the ..//gsfit/win subfolder, which have been compiled assuming a WIN64 architecture. For Win32, please contact us to inquire about alternative options.<br />
<br />
=GSFIT SSW_UPGRADE Installation=<br />
The release version of the IDL GSFIT package is intended to be distributed through the SSW IDL repository [https://www.lmsal.com/solarsoft/]. <br />
Although installed as a stand-alone package, the GSFIT code relies on a series of IDL support routines that are part of the gx_simulator package. Therefore, in addition to installing the gsfit package , the gx_simulator package must be also installed. This installation can be performed by issuing an upgrade command, i.e.<br />
<br />
<pre><br />
IDL> ssw_upgrade,/gsfit,/gx_simulator,/gen,/spawn,/loud,/passive_ftp <br />
</pre><br />
<br />
=GSFIT SSW Instrument Setup=<br />
After the SSW installation is upgraded to include gsfit and gx_simulator packages, to ensure proper functionality, one should also edit the sswidl.bat (on Windows platforms) or cshrc (on Unix or Mac platforms) scripts to include gx_simulator and gsfit in the SSW_INSTR path declaration, i.e.<br />
<pre><br />
set SSW_INSTR=gx_simulator, gsfit [...] <br />
</pre><br />
where [..] denotes any other SSW packages already installed.<br />
<br />
=GSFIT Manual Stand-Alone Installation=<br />
Although '''not reccomended''', one may in principle choose to install the gsfit and gx_simulator packages in standalone directories that are not part of the SSW repositories. However if this (not recommended) option is used, the gsfit and gx_simulator paths should be explicitly added to the IDL !path global variable, i.e. <br />
<br />
and explicitly add this path to your IDL path structure.<br />
<br />
<pre><br />
IDL> !path='..//gsfit/idl:'+!path<br />
IDL> !path='..//gx_simulator/idl:'+!path<br />
</pre><br />
<br />
where '''../''' should be replaced with the explicit paths to the respective local machine repositories.</div>Gnitahttp://ovsa.njit.edu//wiki/index.php?title=GSFIT_Installation&diff=4443GSFIT Installation2019-05-27T11:51:15Z<p>Gnita: /* GSFIT IDL Version Requirements(All Platforms) */</p>
<hr />
<div>[https://github.com/Gelu-Nita/GSFIT GSFIT] is an IDL-widget(GUI)-based spectral fitting package that provides a user-friendly display of [http://www.ovsa.njit.edu/ EOVSA] image cubes and an interface to fast fitting codes (via platform-dependent shared-object libraries). Fits to individual spectra can be done quickly for manual investigation using a GUI application called [http://www.ovsa.njit.edu/wiki/index.php/GSFIT_Help GSFIT], while parallel/multi-core batch processing of selected blocks of data can also be performed using a command prompt application called [http://www.ovsa.njit.edu/wiki/index.php/GSFITCP_Help GSFITCP]. A helper routine called [http://www.ovsa.njit.edu/wiki/index.php/GSFITVIEW_Help GSFITVIEW] allows further display and investigation of the fitting results.<br />
For detailed information about these applications, please visit the pages linked below.<br />
*[[GSFIT Help]]<br />
*[[GSFITCP Help]]<br />
*[[GSFITVIEW Help]]<br />
<br />
Platform specific installation instructions for the GSFIT package are provided on this page.<br />
<br />
=GSFIT IDL Version Requirements(All Platforms)= <br />
<span style="color:red">'''An IDL8.4 version, or higher, is needed for running any of the applications included in this package.'''</span>.<br />
<br />
=GSFIT Linux / Mac OS Requirements=<br />
On Mac and Unix platforms, the gfortran compiler must be also installed to allow automatic compilation of the source code located in the ..//gsfit/unix directory, in order to generate a series of shared libraries, when gsfit is launched for the first time. WARNING: For this action to be successfully completed, the user must have writing rights to the ..//gsfit/unix directory.<br />
<br />
'''Instructions for installing the gfortran compiler, if missing, may be found [http://www.lapk.org/gfortran/gfortran.php?OS=7 here].'''<br />
<br />
=GSFIT Windows OS Requirements=<br />
The GSFIT package is distributed along with a set of dynamic link libraries located in the ..//gsfit/win subfolder, which have been compiled assuming a WIN64 architecture. For Win32, please contact us to inquire about alternative options.<br />
<br />
=GSFIT SSW_UPGRADE Installation=<br />
The release version of the IDL GSFIT package is intended to be distributed through the SSW IDL repository [https://www.lmsal.com/solarsoft/]. <br />
Although installed as a stand-alone package, the GSFIT code relies on a series of IDL support routines that are part of the gx_simulator package. Therefore, in addition to installing the gsfit package , the gx_simulator package must be also installed. This installation can be performed by issuing an upgrade command, i.e.<br />
<br />
<pre><br />
IDL> ssw_upgrade,/gsfit,/gx_simulator,/gen,/spawn,/loud,/passive_ftp <br />
</pre><br />
<br />
=GSFIT SSW Instrument Setup=<br />
After the SSW installation is upgraded to include gsfit and gx_simulator packages, to ensure proper functionality, one should also edit the sswidl.bat (on Windows platforms) or cshrc (on Unix or Mac platforms) scripts to include gx_simulator and gsfit in the SSW_INSTR path declaration, i.e.<br />
<pre><br />
set SSW_INSTR=gx_simulator, gsfit [...] <br />
</pre><br />
where [..] denotes any other SSW packages already installed.<br />
<br />
=GSFIT Manual Stand-Alone Installation=<br />
Although '''not reccomended''', one may in principle choose to install the gsfit and gx_simulator packages in standalone directories that are not part of the SSW repositories. However if this (not recommended) option is used, the gsfit and gx_simulator paths should be explicitly added to the IDL !path global variable, i.e. <br />
<br />
and explicitly add this path to your IDL path structure.<br />
<br />
<pre><br />
IDL> !path='..//gsfit/idl:'+!path<br />
IDL> !path='..//gx_simulator/idl:'+!path<br />
</pre><br />
<br />
where '''../''' should be replaced with the explicit paths to the respective local machine repositories.</div>Gnitahttp://ovsa.njit.edu//wiki/index.php?title=GSFIT_Installation&diff=4442GSFIT Installation2019-05-27T11:50:35Z<p>Gnita: </p>
<hr />
<div>[https://github.com/Gelu-Nita/GSFIT GSFIT] is an IDL-widget(GUI)-based spectral fitting package that provides a user-friendly display of [http://www.ovsa.njit.edu/ EOVSA] image cubes and an interface to fast fitting codes (via platform-dependent shared-object libraries). Fits to individual spectra can be done quickly for manual investigation using a GUI application called [http://www.ovsa.njit.edu/wiki/index.php/GSFIT_Help GSFIT], while parallel/multi-core batch processing of selected blocks of data can also be performed using a command prompt application called [http://www.ovsa.njit.edu/wiki/index.php/GSFITCP_Help GSFITCP]. A helper routine called [http://www.ovsa.njit.edu/wiki/index.php/GSFITVIEW_Help GSFITVIEW] allows further display and investigation of the fitting results.<br />
For detailed information about these applications, please visit the pages linked below.<br />
*[[GSFIT Help]]<br />
*[[GSFITCP Help]]<br />
*[[GSFITVIEW Help]]<br />
<br />
Platform specific installation instructions for the GSFIT package are provided on this page.<br />
<br />
=GSFIT IDL Version Requirements(All Platforms)= <br />
<span style="color:red">An IDL8.4 version, or higher, is needed for running any of the applications included in this package</span>.<br />
<br />
<br />
=GSFIT Linux / Mac OS Requirements=<br />
On Mac and Unix platforms, the gfortran compiler must be also installed to allow automatic compilation of the source code located in the ..//gsfit/unix directory, in order to generate a series of shared libraries, when gsfit is launched for the first time. WARNING: For this action to be successfully completed, the user must have writing rights to the ..//gsfit/unix directory.<br />
<br />
'''Instructions for installing the gfortran compiler, if missing, may be found [http://www.lapk.org/gfortran/gfortran.php?OS=7 here].'''<br />
<br />
=GSFIT Windows OS Requirements=<br />
The GSFIT package is distributed along with a set of dynamic link libraries located in the ..//gsfit/win subfolder, which have been compiled assuming a WIN64 architecture. For Win32, please contact us to inquire about alternative options.<br />
<br />
=GSFIT SSW_UPGRADE Installation=<br />
The release version of the IDL GSFIT package is intended to be distributed through the SSW IDL repository [https://www.lmsal.com/solarsoft/]. <br />
Although installed as a stand-alone package, the GSFIT code relies on a series of IDL support routines that are part of the gx_simulator package. Therefore, in addition to installing the gsfit package , the gx_simulator package must be also installed. This installation can be performed by issuing an upgrade command, i.e.<br />
<br />
<pre><br />
IDL> ssw_upgrade,/gsfit,/gx_simulator,/gen,/spawn,/loud,/passive_ftp <br />
</pre><br />
<br />
=GSFIT SSW Instrument Setup=<br />
After the SSW installation is upgraded to include gsfit and gx_simulator packages, to ensure proper functionality, one should also edit the sswidl.bat (on Windows platforms) or cshrc (on Unix or Mac platforms) scripts to include gx_simulator and gsfit in the SSW_INSTR path declaration, i.e.<br />
<pre><br />
set SSW_INSTR=gx_simulator, gsfit [...] <br />
</pre><br />
where [..] denotes any other SSW packages already installed.<br />
<br />
=GSFIT Manual Stand-Alone Installation=<br />
Although '''not reccomended''', one may in principle choose to install the gsfit and gx_simulator packages in standalone directories that are not part of the SSW repositories. However if this (not recommended) option is used, the gsfit and gx_simulator paths should be explicitly added to the IDL !path global variable, i.e. <br />
<br />
and explicitly add this path to your IDL path structure.<br />
<br />
<pre><br />
IDL> !path='..//gsfit/idl:'+!path<br />
IDL> !path='..//gx_simulator/idl:'+!path<br />
</pre><br />
<br />
where '''../''' should be replaced with the explicit paths to the respective local machine repositories.</div>Gnitahttp://ovsa.njit.edu//wiki/index.php?title=GSFIT_Installation&diff=4441GSFIT Installation2019-05-27T11:49:50Z<p>Gnita: </p>
<hr />
<div>[https://github.com/Gelu-Nita/GSFIT GSFIT] is an IDL-widget(GUI)-based spectral fitting package that provides a user-friendly display of [http://www.ovsa.njit.edu/ EOVSA] image cubes and an interface to fast fitting codes (via platform-dependent shared-object libraries). Fits to individual spectra can be done quickly for manual investigation using a GUI application called [http://www.ovsa.njit.edu/wiki/index.php/GSFIT_Help GSFIT], while parallel/multi-core batch processing of selected blocks of data can also be performed using a command prompt application called [http://www.ovsa.njit.edu/wiki/index.php/GSFITCP_Help GSFITCP]. A helper routine called [http://www.ovsa.njit.edu/wiki/index.php/GSFITVIEW_Help GSFITVIEW] allows further display and investigation of the fitting results.<br />
For detailed information about these applications, please visit the pages linked below.<br />
*[[GSFIT Help]]<br />
*[[GSFITCP Help]]<br />
*[[GSFITVIEW Help]]<br />
<br />
Platform specific installation instructions for the GSFIT package are provided on this page.<br />
<br />
=GSFIT IDL Version Requirements(All Platforms)= <br />
{{font color|red|An IDL8.4 version, or higher, is needed for running any of the applications included in this package}}.<br />
<br />
<br />
=GSFIT Linux / Mac OS Requirements=<br />
On Mac and Unix platforms, the gfortran compiler must be also installed to allow automatic compilation of the source code located in the ..//gsfit/unix directory, in order to generate a series of shared libraries, when gsfit is launched for the first time. WARNING: For this action to be successfully completed, the user must have writing rights to the ..//gsfit/unix directory.<br />
<br />
'''Instructions for installing the gfortran compiler, if missing, may be found [http://www.lapk.org/gfortran/gfortran.php?OS=7 here].'''<br />
<br />
=GSFIT Windows OS Requirements=<br />
The GSFIT package is distributed along with a set of dynamic link libraries located in the ..//gsfit/win subfolder, which have been compiled assuming a WIN64 architecture. For Win32, please contact us to inquire about alternative options.<br />
<br />
=GSFIT SSW_UPGRADE Installation=<br />
The release version of the IDL GSFIT package is intended to be distributed through the SSW IDL repository [https://www.lmsal.com/solarsoft/]. <br />
Although installed as a stand-alone package, the GSFIT code relies on a series of IDL support routines that are part of the gx_simulator package. Therefore, in addition to installing the gsfit package , the gx_simulator package must be also installed. This installation can be performed by issuing an upgrade command, i.e.<br />
<br />
<pre><br />
IDL> ssw_upgrade,/gsfit,/gx_simulator,/gen,/spawn,/loud,/passive_ftp <br />
</pre><br />
<br />
=GSFIT SSW Instrument Setup=<br />
After the SSW installation is upgraded to include gsfit and gx_simulator packages, to ensure proper functionality, one should also edit the sswidl.bat (on Windows platforms) or cshrc (on Unix or Mac platforms) scripts to include gx_simulator and gsfit in the SSW_INSTR path declaration, i.e.<br />
<pre><br />
set SSW_INSTR=gx_simulator, gsfit [...] <br />
</pre><br />
where [..] denotes any other SSW packages already installed.<br />
<br />
=GSFIT Manual Stand-Alone Installation=<br />
Although '''not reccomended''', one may in principle choose to install the gsfit and gx_simulator packages in standalone directories that are not part of the SSW repositories. However if this (not recommended) option is used, the gsfit and gx_simulator paths should be explicitly added to the IDL !path global variable, i.e. <br />
<br />
and explicitly add this path to your IDL path structure.<br />
<br />
<pre><br />
IDL> !path='..//gsfit/idl:'+!path<br />
IDL> !path='..//gx_simulator/idl:'+!path<br />
</pre><br />
<br />
where '''../''' should be replaced with the explicit paths to the respective local machine repositories.</div>Gnitahttp://ovsa.njit.edu//wiki/index.php?title=GSFIT_Installation&diff=4440GSFIT Installation2019-05-27T11:49:37Z<p>Gnita: </p>
<hr />
<div>[https://github.com/Gelu-Nita/GSFIT GSFIT] is an IDL-widget(GUI)-based spectral fitting package that provides a user-friendly display of [http://www.ovsa.njit.edu/ EOVSA] image cubes and an interface to fast fitting codes (via platform-dependent shared-object libraries). Fits to individual spectra can be done quickly for manual investigation using a GUI application called [http://www.ovsa.njit.edu/wiki/index.php/GSFIT_Help GSFIT], while parallel/multi-core batch processing of selected blocks of data can also be performed using a command prompt application called [http://www.ovsa.njit.edu/wiki/index.php/GSFITCP_Help GSFITCP]. A helper routine called [http://www.ovsa.njit.edu/wiki/index.php/GSFITVIEW_Help GSFITVIEW] allows further display and investigation of the fitting results.<br />
For detailed information about these applications, please visit the pages linked below.<br />
*[[GSFIT Help]]<br />
*[[GSFITCP Help]]<br />
*[[GSFITVIEW Help]]<br />
<br />
Platform specific installation instructions for the GSFIT package are provided on this page.<br />
<br />
=GSFIT IDL Version Requirements(All Platforms)= <br />
{{font color|red| An IDL8.4 version, or higher, is needed for running any of the applications included in this package}}.<br />
<br />
<br />
=GSFIT Linux / Mac OS Requirements=<br />
On Mac and Unix platforms, the gfortran compiler must be also installed to allow automatic compilation of the source code located in the ..//gsfit/unix directory, in order to generate a series of shared libraries, when gsfit is launched for the first time. WARNING: For this action to be successfully completed, the user must have writing rights to the ..//gsfit/unix directory.<br />
<br />
'''Instructions for installing the gfortran compiler, if missing, may be found [http://www.lapk.org/gfortran/gfortran.php?OS=7 here].'''<br />
<br />
=GSFIT Windows OS Requirements=<br />
The GSFIT package is distributed along with a set of dynamic link libraries located in the ..//gsfit/win subfolder, which have been compiled assuming a WIN64 architecture. For Win32, please contact us to inquire about alternative options.<br />
<br />
=GSFIT SSW_UPGRADE Installation=<br />
The release version of the IDL GSFIT package is intended to be distributed through the SSW IDL repository [https://www.lmsal.com/solarsoft/]. <br />
Although installed as a stand-alone package, the GSFIT code relies on a series of IDL support routines that are part of the gx_simulator package. Therefore, in addition to installing the gsfit package , the gx_simulator package must be also installed. This installation can be performed by issuing an upgrade command, i.e.<br />
<br />
<pre><br />
IDL> ssw_upgrade,/gsfit,/gx_simulator,/gen,/spawn,/loud,/passive_ftp <br />
</pre><br />
<br />
=GSFIT SSW Instrument Setup=<br />
After the SSW installation is upgraded to include gsfit and gx_simulator packages, to ensure proper functionality, one should also edit the sswidl.bat (on Windows platforms) or cshrc (on Unix or Mac platforms) scripts to include gx_simulator and gsfit in the SSW_INSTR path declaration, i.e.<br />
<pre><br />
set SSW_INSTR=gx_simulator, gsfit [...] <br />
</pre><br />
where [..] denotes any other SSW packages already installed.<br />
<br />
=GSFIT Manual Stand-Alone Installation=<br />
Although '''not reccomended''', one may in principle choose to install the gsfit and gx_simulator packages in standalone directories that are not part of the SSW repositories. However if this (not recommended) option is used, the gsfit and gx_simulator paths should be explicitly added to the IDL !path global variable, i.e. <br />
<br />
and explicitly add this path to your IDL path structure.<br />
<br />
<pre><br />
IDL> !path='..//gsfit/idl:'+!path<br />
IDL> !path='..//gx_simulator/idl:'+!path<br />
</pre><br />
<br />
where '''../''' should be replaced with the explicit paths to the respective local machine repositories.</div>Gnitahttp://ovsa.njit.edu//wiki/index.php?title=GSFIT_Installation&diff=4439GSFIT Installation2019-05-27T11:48:55Z<p>Gnita: </p>
<hr />
<div>[https://github.com/Gelu-Nita/GSFIT GSFIT] is an IDL-widget(GUI)-based spectral fitting package that provides a user-friendly display of [http://www.ovsa.njit.edu/ EOVSA] image cubes and an interface to fast fitting codes (via platform-dependent shared-object libraries). Fits to individual spectra can be done quickly for manual investigation using a GUI application called [http://www.ovsa.njit.edu/wiki/index.php/GSFIT_Help GSFIT], while parallel/multi-core batch processing of selected blocks of data can also be performed using a command prompt application called [http://www.ovsa.njit.edu/wiki/index.php/GSFITCP_Help GSFITCP]. A helper routine called [http://www.ovsa.njit.edu/wiki/index.php/GSFITVIEW_Help GSFITVIEW] allows further display and investigation of the fitting results.<br />
For detailed information about these applications, please visit the pages linked below.<br />
*[[GSFIT Help]]<br />
*[[GSFITCP Help]]<br />
*[[GSFITVIEW Help]]<br />
<br />
Platform specific installation instructions for the GSFIT package are provided on this page.<br />
<br />
=GSFIT IDL Version Requirements(All Platforms)= <br />
The current version of the GSFIT package relies on functionality that has been introduced only in IDL8.4. {{font color|red| '''Therefore, an IDL8.4 version, or higher, is needed for running any of the applications included in this package'''}}.<br />
<br />
<br />
=GSFIT Linux / Mac OS Requirements=<br />
On Mac and Unix platforms, the gfortran compiler must be also installed to allow automatic compilation of the source code located in the ..//gsfit/unix directory, in order to generate a series of shared libraries, when gsfit is launched for the first time. WARNING: For this action to be successfully completed, the user must have writing rights to the ..//gsfit/unix directory.<br />
<br />
'''Instructions for installing the gfortran compiler, if missing, may be found [http://www.lapk.org/gfortran/gfortran.php?OS=7 here].'''<br />
<br />
=GSFIT Windows OS Requirements=<br />
The GSFIT package is distributed along with a set of dynamic link libraries located in the ..//gsfit/win subfolder, which have been compiled assuming a WIN64 architecture. For Win32, please contact us to inquire about alternative options.<br />
<br />
=GSFIT SSW_UPGRADE Installation=<br />
The release version of the IDL GSFIT package is intended to be distributed through the SSW IDL repository [https://www.lmsal.com/solarsoft/]. <br />
Although installed as a stand-alone package, the GSFIT code relies on a series of IDL support routines that are part of the gx_simulator package. Therefore, in addition to installing the gsfit package , the gx_simulator package must be also installed. This installation can be performed by issuing an upgrade command, i.e.<br />
<br />
<pre><br />
IDL> ssw_upgrade,/gsfit,/gx_simulator,/gen,/spawn,/loud,/passive_ftp <br />
</pre><br />
<br />
=GSFIT SSW Instrument Setup=<br />
After the SSW installation is upgraded to include gsfit and gx_simulator packages, to ensure proper functionality, one should also edit the sswidl.bat (on Windows platforms) or cshrc (on Unix or Mac platforms) scripts to include gx_simulator and gsfit in the SSW_INSTR path declaration, i.e.<br />
<pre><br />
set SSW_INSTR=gx_simulator, gsfit [...] <br />
</pre><br />
where [..] denotes any other SSW packages already installed.<br />
<br />
=GSFIT Manual Stand-Alone Installation=<br />
Although '''not reccomended''', one may in principle choose to install the gsfit and gx_simulator packages in standalone directories that are not part of the SSW repositories. However if this (not recommended) option is used, the gsfit and gx_simulator paths should be explicitly added to the IDL !path global variable, i.e. <br />
<br />
and explicitly add this path to your IDL path structure.<br />
<br />
<pre><br />
IDL> !path='..//gsfit/idl:'+!path<br />
IDL> !path='..//gx_simulator/idl:'+!path<br />
</pre><br />
<br />
where '''../''' should be replaced with the explicit paths to the respective local machine repositories.</div>Gnitahttp://ovsa.njit.edu//wiki/index.php?title=GSFIT_Installation&diff=4438GSFIT Installation2019-05-27T11:48:00Z<p>Gnita: </p>
<hr />
<div>[https://github.com/Gelu-Nita/GSFIT GSFIT] is an IDL-widget(GUI)-based spectral fitting package that provides a user-friendly display of [http://www.ovsa.njit.edu/ EOVSA] image cubes and an interface to fast fitting codes (via platform-dependent shared-object libraries). Fits to individual spectra can be done quickly for manual investigation using a GUI application called [http://www.ovsa.njit.edu/wiki/index.php/GSFIT_Help GSFIT], while parallel/multi-core batch processing of selected blocks of data can also be performed using a command prompt application called [http://www.ovsa.njit.edu/wiki/index.php/GSFITCP_Help GSFITCP]. A helper routine called [http://www.ovsa.njit.edu/wiki/index.php/GSFITVIEW_Help GSFITVIEW] allows further display and investigation of the fitting results.<br />
For detailed information about these applications, please visit the pages linked below.<br />
*[[GSFIT Help]]<br />
*[[GSFITCP Help]]<br />
*[[GSFITVIEW Help]]<br />
<br />
Platform specific installation instructions for the GSFIT package are provided on this page.<br />
<br />
=GSFIT IDL Version Requirements(All Platforms)= <br />
The current version of the GSFIT package relies on functionality that has been introduced only in IDL8.4. {{font color|red|This text is different}} Therefore, an IDL8.4 version, or higher, is needed for running any of the applications included in this package.<br />
<br />
<br />
=GSFIT Linux / Mac OS Requirements=<br />
On Mac and Unix platforms, the gfortran compiler must be also installed to allow automatic compilation of the source code located in the ..//gsfit/unix directory, in order to generate a series of shared libraries, when gsfit is launched for the first time. WARNING: For this action to be successfully completed, the user must have writing rights to the ..//gsfit/unix directory.<br />
<br />
'''Instructions for installing the gfortran compiler, if missing, may be found [http://www.lapk.org/gfortran/gfortran.php?OS=7 here].'''<br />
<br />
=GSFIT Windows OS Requirements=<br />
The GSFIT package is distributed along with a set of dynamic link libraries located in the ..//gsfit/win subfolder, which have been compiled assuming a WIN64 architecture. For Win32, please contact us to inquire about alternative options.<br />
<br />
=GSFIT SSW_UPGRADE Installation=<br />
The release version of the IDL GSFIT package is intended to be distributed through the SSW IDL repository [https://www.lmsal.com/solarsoft/]. <br />
Although installed as a stand-alone package, the GSFIT code relies on a series of IDL support routines that are part of the gx_simulator package. Therefore, in addition to installing the gsfit package , the gx_simulator package must be also installed. This installation can be performed by issuing an upgrade command, i.e.<br />
<br />
<pre><br />
IDL> ssw_upgrade,/gsfit,/gx_simulator,/gen,/spawn,/loud,/passive_ftp <br />
</pre><br />
<br />
=GSFIT SSW Instrument Setup=<br />
After the SSW installation is upgraded to include gsfit and gx_simulator packages, to ensure proper functionality, one should also edit the sswidl.bat (on Windows platforms) or cshrc (on Unix or Mac platforms) scripts to include gx_simulator and gsfit in the SSW_INSTR path declaration, i.e.<br />
<pre><br />
set SSW_INSTR=gx_simulator, gsfit [...] <br />
</pre><br />
where [..] denotes any other SSW packages already installed.<br />
<br />
=GSFIT Manual Stand-Alone Installation=<br />
Although '''not reccomended''', one may in principle choose to install the gsfit and gx_simulator packages in standalone directories that are not part of the SSW repositories. However if this (not recommended) option is used, the gsfit and gx_simulator paths should be explicitly added to the IDL !path global variable, i.e. <br />
<br />
and explicitly add this path to your IDL path structure.<br />
<br />
<pre><br />
IDL> !path='..//gsfit/idl:'+!path<br />
IDL> !path='..//gx_simulator/idl:'+!path<br />
</pre><br />
<br />
where '''../''' should be replaced with the explicit paths to the respective local machine repositories.</div>Gnitahttp://ovsa.njit.edu//wiki/index.php?title=GSFIT_Installation&diff=4437GSFIT Installation2019-05-27T11:45:23Z<p>Gnita: </p>
<hr />
<div>[https://github.com/Gelu-Nita/GSFIT GSFIT] is an IDL-widget(GUI)-based spectral fitting package that provides a user-friendly display of [http://www.ovsa.njit.edu/ EOVSA] image cubes and an interface to fast fitting codes (via platform-dependent shared-object libraries). Fits to individual spectra can be done quickly for manual investigation using a GUI application called [http://www.ovsa.njit.edu/wiki/index.php/GSFIT_Help GSFIT], while parallel/multi-core batch processing of selected blocks of data can also be performed using a command prompt application called [http://www.ovsa.njit.edu/wiki/index.php/GSFITCP_Help GSFITCP]. A helper routine called [http://www.ovsa.njit.edu/wiki/index.php/GSFITVIEW_Help GSFITVIEW] allows further display and investigation of the fitting results.<br />
For detailed information about these applications, please visit the pages linked below.<br />
*[[GSFIT Help]]<br />
*[[GSFITCP Help]]<br />
*[[GSFITVIEW Help]]<br />
<br />
Platform specific installation instructions for the GSFIT package are provided on this page.<br />
<br />
=GSFIT IDL Version Requirements(All Platforms)= <br />
The current version of the GSFIT package relies on functionality that has been introduced only in IDL8.4. Therefore, an IDL8.4 version, or higher, is needed for running any of the applications included in this package.<br />
<br />
<br />
=GSFIT Linux / Mac OS Requirements=<br />
On Mac and Unix platforms, the gfortran compiler must be also installed to allow automatic compilation of the source code located in the ..//gsfit/unix directory, in order to generate a series of shared libraries, when gsfit is launched for the first time. WARNING: For this action to be successfully completed, the user must have writing rights to the ..//gsfit/unix directory.<br />
<br />
'''Instructions for installing the gfortran compiler, if missing, may be found [http://www.lapk.org/gfortran/gfortran.php?OS=7 here].'''<br />
<br />
=GSFIT Windows OS Requirements=<br />
The GSFIT package is distributed along with a set of dynamic link libraries located in the ..//gsfit/win subfolder, which have been compiled assuming a WIN64 architecture. For Win32, please contact us to inquire about alternative options.<br />
<br />
=GSFIT SSW_UPGRADE Installation=<br />
The release version of the IDL GSFIT package is intended to be distributed through the SSW IDL repository [https://www.lmsal.com/solarsoft/]. <br />
Although installed as a stand-alone package, the GSFIT code relies on a series of IDL support routines that are part of the gx_simulator package. Therefore, in addition to installing the gsfit package , the gx_simulator package must be also installed. This installation can be performed by issuing an upgrade command, i.e.<br />
<br />
<pre><br />
IDL> ssw_upgrade,/gsfit,/gx_simulator,/gen,/spawn,/loud,/passive_ftp <br />
</pre><br />
<br />
=GSFIT SSW Instrument Setup=<br />
After the SSW installation is upgraded to include gsfit and gx_simulator packages, to ensure proper functionality, one should also edit the sswidl.bat (on Windows platforms) or cshrc (on Unix or Mac platforms) scripts to include gx_simulator and gsfit in the SSW_INSTR path declaration, i.e.<br />
<pre><br />
set SSW_INSTR=gx_simulator, gsfit [...] <br />
</pre><br />
where [..] denotes any other SSW packages already installed.<br />
<br />
=GSFIT Manual Stand-Alone Installation=<br />
Although '''not reccomended''', one may in principle choose to install the gsfit and gx_simulator packages in standalone directories that are not part of the SSW repositories. However if this (not recommended) option is used, the gsfit and gx_simulator paths should be explicitly added to the IDL !path global variable, i.e. <br />
<br />
and explicitly add this path to your IDL path structure.<br />
<br />
<pre><br />
IDL> !path='..//gsfit/idl:'+!path<br />
IDL> !path='..//gx_simulator/idl:'+!path<br />
</pre><br />
<br />
where '''../''' should be replaced with the explicit paths to the respective local machine repositories.</div>Gnitahttp://ovsa.njit.edu//wiki/index.php?title=GSFIT_Installation&diff=4436GSFIT Installation2019-05-27T11:39:42Z<p>Gnita: /* GSFIT Linux / Mac OS Requirements */</p>
<hr />
<div>[https://github.com/Gelu-Nita/GSFIT GSFIT] is an IDL-widget(GUI)-based spectral fitting package that provides a user-friendly display of [http://www.ovsa.njit.edu/ EOVSA] image cubes and an interface to fast fitting codes (via platform-dependent shared-object libraries). Fits to individual spectra can be done quickly for manual investigation using a GUI application called [http://www.ovsa.njit.edu/wiki/index.php/GSFIT_Help GSFIT], while parallel/multi-core batch processing of selected blocks of data can also be performed using a command prompt application called [http://www.ovsa.njit.edu/wiki/index.php/GSFITCP_Help GSFITCP]. A helper routine called [http://www.ovsa.njit.edu/wiki/index.php/GSFITVIEW_Help GSFITVIEW] allows further display and investigation of the fitting results.<br />
For detailed information about these applications, please visit the pages linked below.<br />
*[[GSFIT Help]]<br />
*[[GSFITCP Help]]<br />
*[[GSFITVIEW Help]]<br />
<br />
Platform specific installation instructions for the GSFIT package are provided on this page.<br />
<br />
=GSFIT Linux / Mac OS Requirements=<br />
On Mac and Unix platforms, the gfortran compiler must be also installed to allow automatic compilation of the source code located in the ..//gsfit/unix directory, in order to generate a series of shared libraries, when gsfit is launched for the first time. WARNING: For this action to be successfully completed, the user must have writing rights to the ..//gsfit/unix directory.<br />
<br />
'''Instructions for installing the gfortran compiler, if missing, may be found [http://www.lapk.org/gfortran/gfortran.php?OS=7 here].'''<br />
<br />
=GSFIT Windows OS Requirements=<br />
The GSFIT package is distributed along with a set of dynamic link libraries located in the ..//gsfit/win subfolder, which have been compiled assuming a WIN64 architecture. For Win32, please contact us to inquire about alternative options.<br />
<br />
=GSFIT SSW_UPGRADE Installation=<br />
The release version of the IDL GSFIT package is intended to be distributed through the SSW IDL repository [https://www.lmsal.com/solarsoft/]. <br />
Although installed as a stand-alone package, the GSFIT code relies on a series of IDL support routines that are part of the gx_simulator package. Therefore, in addition to installing the gsfit package , the gx_simulator package must be also installed. This installation can be performed by issuing an upgrade command, i.e.<br />
<br />
<pre><br />
IDL> ssw_upgrade,/gsfit,/gx_simulator,/gen,/spawn,/loud,/passive_ftp <br />
</pre><br />
<br />
=GSFIT SSW Instrument Setup=<br />
After the SSW installation is upgraded to include gsfit and gx_simulator packages, to ensure proper functionality, one should also edit the sswidl.bat (on Windows platforms) or cshrc (on Unix or Mac platforms) scripts to include gx_simulator and gsfit in the SSW_INSTR path declaration, i.e.<br />
<pre><br />
set SSW_INSTR=gx_simulator, gsfit [...] <br />
</pre><br />
where [..] denotes any other SSW packages already installed.<br />
<br />
=GSFIT Manual Stand-Alone Installation=<br />
Although '''not reccomended''', one may in principle choose to install the gsfit and gx_simulator packages in standalone directories that are not part of the SSW repositories. However if this (not recommended) option is used, the gsfit and gx_simulator paths should be explicitly added to the IDL !path global variable, i.e. <br />
<br />
and explicitly add this path to your IDL path structure.<br />
<br />
<pre><br />
IDL> !path='..//gsfit/idl:'+!path<br />
IDL> !path='..//gx_simulator/idl:'+!path<br />
</pre><br />
<br />
where '''../''' should be replaced with the explicit paths to the respective local machine repositories.</div>Gnitahttp://ovsa.njit.edu//wiki/index.php?title=GSFIT_Installation&diff=4435GSFIT Installation2019-05-27T11:39:32Z<p>Gnita: /* GSFIT Linux / Mac OS Requirements */</p>
<hr />
<div>[https://github.com/Gelu-Nita/GSFIT GSFIT] is an IDL-widget(GUI)-based spectral fitting package that provides a user-friendly display of [http://www.ovsa.njit.edu/ EOVSA] image cubes and an interface to fast fitting codes (via platform-dependent shared-object libraries). Fits to individual spectra can be done quickly for manual investigation using a GUI application called [http://www.ovsa.njit.edu/wiki/index.php/GSFIT_Help GSFIT], while parallel/multi-core batch processing of selected blocks of data can also be performed using a command prompt application called [http://www.ovsa.njit.edu/wiki/index.php/GSFITCP_Help GSFITCP]. A helper routine called [http://www.ovsa.njit.edu/wiki/index.php/GSFITVIEW_Help GSFITVIEW] allows further display and investigation of the fitting results.<br />
For detailed information about these applications, please visit the pages linked below.<br />
*[[GSFIT Help]]<br />
*[[GSFITCP Help]]<br />
*[[GSFITVIEW Help]]<br />
<br />
Platform specific installation instructions for the GSFIT package are provided on this page.<br />
<br />
=GSFIT Linux / Mac OS Requirements=<br />
On Mac and Unix platforms, the gfortran compiler must be also installed to allow automatic compilation of the source code located in the ..//gsfit/unix directory, in order to generate a series of shared libraries, when gsfit is launched for the first time. WARNING: For this action to be successfully completed, the user must have writing rights to the ..//gsfit/unix directory.<br />
<br />
<br />
'''Instructions for installing the gfortran compiler, if missing, may be found [http://www.lapk.org/gfortran/gfortran.php?OS=7 here].'''<br />
<br />
=GSFIT Windows OS Requirements=<br />
The GSFIT package is distributed along with a set of dynamic link libraries located in the ..//gsfit/win subfolder, which have been compiled assuming a WIN64 architecture. For Win32, please contact us to inquire about alternative options.<br />
<br />
=GSFIT SSW_UPGRADE Installation=<br />
The release version of the IDL GSFIT package is intended to be distributed through the SSW IDL repository [https://www.lmsal.com/solarsoft/]. <br />
Although installed as a stand-alone package, the GSFIT code relies on a series of IDL support routines that are part of the gx_simulator package. Therefore, in addition to installing the gsfit package , the gx_simulator package must be also installed. This installation can be performed by issuing an upgrade command, i.e.<br />
<br />
<pre><br />
IDL> ssw_upgrade,/gsfit,/gx_simulator,/gen,/spawn,/loud,/passive_ftp <br />
</pre><br />
<br />
=GSFIT SSW Instrument Setup=<br />
After the SSW installation is upgraded to include gsfit and gx_simulator packages, to ensure proper functionality, one should also edit the sswidl.bat (on Windows platforms) or cshrc (on Unix or Mac platforms) scripts to include gx_simulator and gsfit in the SSW_INSTR path declaration, i.e.<br />
<pre><br />
set SSW_INSTR=gx_simulator, gsfit [...] <br />
</pre><br />
where [..] denotes any other SSW packages already installed.<br />
<br />
=GSFIT Manual Stand-Alone Installation=<br />
Although '''not reccomended''', one may in principle choose to install the gsfit and gx_simulator packages in standalone directories that are not part of the SSW repositories. However if this (not recommended) option is used, the gsfit and gx_simulator paths should be explicitly added to the IDL !path global variable, i.e. <br />
<br />
and explicitly add this path to your IDL path structure.<br />
<br />
<pre><br />
IDL> !path='..//gsfit/idl:'+!path<br />
IDL> !path='..//gx_simulator/idl:'+!path<br />
</pre><br />
<br />
where '''../''' should be replaced with the explicit paths to the respective local machine repositories.</div>Gnitahttp://ovsa.njit.edu//wiki/index.php?title=GSFIT_Installation&diff=4434GSFIT Installation2019-05-27T11:38:43Z<p>Gnita: /* GSFIT Linux / Mac OS Requirements */</p>
<hr />
<div>[https://github.com/Gelu-Nita/GSFIT GSFIT] is an IDL-widget(GUI)-based spectral fitting package that provides a user-friendly display of [http://www.ovsa.njit.edu/ EOVSA] image cubes and an interface to fast fitting codes (via platform-dependent shared-object libraries). Fits to individual spectra can be done quickly for manual investigation using a GUI application called [http://www.ovsa.njit.edu/wiki/index.php/GSFIT_Help GSFIT], while parallel/multi-core batch processing of selected blocks of data can also be performed using a command prompt application called [http://www.ovsa.njit.edu/wiki/index.php/GSFITCP_Help GSFITCP]. A helper routine called [http://www.ovsa.njit.edu/wiki/index.php/GSFITVIEW_Help GSFITVIEW] allows further display and investigation of the fitting results.<br />
For detailed information about these applications, please visit the pages linked below.<br />
*[[GSFIT Help]]<br />
*[[GSFITCP Help]]<br />
*[[GSFITVIEW Help]]<br />
<br />
Platform specific installation instructions for the GSFIT package are provided on this page.<br />
<br />
=GSFIT Linux / Mac OS Requirements=<br />
On Mac and Unix platforms, the gfortran compiler must be also installed to allow automatic compilation of the source code located in the ..//gsfit/unix directory, in order to generate a series of shared libraries, when gsfit is launched for the first time. '''Instructions for installing the gfortran compiler, if missing, may be found [http://www.lapk.org/gfortran/gfortran.php?OS=7 here].<br />
'''<br />
WARNING: For this action to be successfully completed, the user must have writing rights to the ..//gsfit/unix directory.<br />
<br />
=GSFIT Windows OS Requirements=<br />
The GSFIT package is distributed along with a set of dynamic link libraries located in the ..//gsfit/win subfolder, which have been compiled assuming a WIN64 architecture. For Win32, please contact us to inquire about alternative options.<br />
<br />
=GSFIT SSW_UPGRADE Installation=<br />
The release version of the IDL GSFIT package is intended to be distributed through the SSW IDL repository [https://www.lmsal.com/solarsoft/]. <br />
Although installed as a stand-alone package, the GSFIT code relies on a series of IDL support routines that are part of the gx_simulator package. Therefore, in addition to installing the gsfit package , the gx_simulator package must be also installed. This installation can be performed by issuing an upgrade command, i.e.<br />
<br />
<pre><br />
IDL> ssw_upgrade,/gsfit,/gx_simulator,/gen,/spawn,/loud,/passive_ftp <br />
</pre><br />
<br />
=GSFIT SSW Instrument Setup=<br />
After the SSW installation is upgraded to include gsfit and gx_simulator packages, to ensure proper functionality, one should also edit the sswidl.bat (on Windows platforms) or cshrc (on Unix or Mac platforms) scripts to include gx_simulator and gsfit in the SSW_INSTR path declaration, i.e.<br />
<pre><br />
set SSW_INSTR=gx_simulator, gsfit [...] <br />
</pre><br />
where [..] denotes any other SSW packages already installed.<br />
<br />
=GSFIT Manual Stand-Alone Installation=<br />
Although '''not reccomended''', one may in principle choose to install the gsfit and gx_simulator packages in standalone directories that are not part of the SSW repositories. However if this (not recommended) option is used, the gsfit and gx_simulator paths should be explicitly added to the IDL !path global variable, i.e. <br />
<br />
and explicitly add this path to your IDL path structure.<br />
<br />
<pre><br />
IDL> !path='..//gsfit/idl:'+!path<br />
IDL> !path='..//gx_simulator/idl:'+!path<br />
</pre><br />
<br />
where '''../''' should be replaced with the explicit paths to the respective local machine repositories.</div>Gnitahttp://ovsa.njit.edu//wiki/index.php?title=GSFIT_Installation&diff=4433GSFIT Installation2019-05-27T11:38:18Z<p>Gnita: /* GSFIT Linux / Mac OS Requirements */</p>
<hr />
<div>[https://github.com/Gelu-Nita/GSFIT GSFIT] is an IDL-widget(GUI)-based spectral fitting package that provides a user-friendly display of [http://www.ovsa.njit.edu/ EOVSA] image cubes and an interface to fast fitting codes (via platform-dependent shared-object libraries). Fits to individual spectra can be done quickly for manual investigation using a GUI application called [http://www.ovsa.njit.edu/wiki/index.php/GSFIT_Help GSFIT], while parallel/multi-core batch processing of selected blocks of data can also be performed using a command prompt application called [http://www.ovsa.njit.edu/wiki/index.php/GSFITCP_Help GSFITCP]. A helper routine called [http://www.ovsa.njit.edu/wiki/index.php/GSFITVIEW_Help GSFITVIEW] allows further display and investigation of the fitting results.<br />
For detailed information about these applications, please visit the pages linked below.<br />
*[[GSFIT Help]]<br />
*[[GSFITCP Help]]<br />
*[[GSFITVIEW Help]]<br />
<br />
Platform specific installation instructions for the GSFIT package are provided on this page.<br />
<br />
=GSFIT Linux / Mac OS Requirements=<br />
On Mac and Unix platforms, the gfortran compiler must be also installed to allow automatic compilation of the source code located in the ..//gsfit/unix directory, in order to generate a series of shared libraries, when gsfit is launched for the first time. '''Instructions for installing the gfortran compiler, if missing, may be found [[http://www.lapk.org/gfortran/gfortran.php?OS=7] here].<br />
'''<br />
WARNING: For this action to be successfully completed, the user must have writing rights to the ..//gsfit/unix directory.<br />
<br />
=GSFIT Windows OS Requirements=<br />
The GSFIT package is distributed along with a set of dynamic link libraries located in the ..//gsfit/win subfolder, which have been compiled assuming a WIN64 architecture. For Win32, please contact us to inquire about alternative options.<br />
<br />
=GSFIT SSW_UPGRADE Installation=<br />
The release version of the IDL GSFIT package is intended to be distributed through the SSW IDL repository [https://www.lmsal.com/solarsoft/]. <br />
Although installed as a stand-alone package, the GSFIT code relies on a series of IDL support routines that are part of the gx_simulator package. Therefore, in addition to installing the gsfit package , the gx_simulator package must be also installed. This installation can be performed by issuing an upgrade command, i.e.<br />
<br />
<pre><br />
IDL> ssw_upgrade,/gsfit,/gx_simulator,/gen,/spawn,/loud,/passive_ftp <br />
</pre><br />
<br />
=GSFIT SSW Instrument Setup=<br />
After the SSW installation is upgraded to include gsfit and gx_simulator packages, to ensure proper functionality, one should also edit the sswidl.bat (on Windows platforms) or cshrc (on Unix or Mac platforms) scripts to include gx_simulator and gsfit in the SSW_INSTR path declaration, i.e.<br />
<pre><br />
set SSW_INSTR=gx_simulator, gsfit [...] <br />
</pre><br />
where [..] denotes any other SSW packages already installed.<br />
<br />
=GSFIT Manual Stand-Alone Installation=<br />
Although '''not reccomended''', one may in principle choose to install the gsfit and gx_simulator packages in standalone directories that are not part of the SSW repositories. However if this (not recommended) option is used, the gsfit and gx_simulator paths should be explicitly added to the IDL !path global variable, i.e. <br />
<br />
and explicitly add this path to your IDL path structure.<br />
<br />
<pre><br />
IDL> !path='..//gsfit/idl:'+!path<br />
IDL> !path='..//gx_simulator/idl:'+!path<br />
</pre><br />
<br />
where '''../''' should be replaced with the explicit paths to the respective local machine repositories.</div>Gnitahttp://ovsa.njit.edu//wiki/index.php?title=GSFIT_Installation&diff=4221GSFIT Installation2019-05-18T21:46:21Z<p>Gnita: /* GSFIT SSW Instrument Setup */</p>
<hr />
<div>[https://github.com/Gelu-Nita/GSFIT GSFIT] is an IDL-widget(GUI)-based spectral fitting package that provides a user-friendly display of [http://www.ovsa.njit.edu/ EOVSA] image cubes and an interface to fast fitting codes (via platform-dependent shared-object libraries). Fits to individual spectra can be done quickly for manual investigation using a GUI application called [http://www.ovsa.njit.edu/wiki/index.php/GSFIT_Help GSFIT], while parallel/multi-core batch processing of selected blocks of data can also be performed using a command prompt application called [http://www.ovsa.njit.edu/wiki/index.php/GSFITCP_Help GSFITCP]. A helper routine called [http://www.ovsa.njit.edu/wiki/index.php/GSFITVIEW_Help GSFITVIEW] allows further display and investigation of the fitting results.<br />
For detailed information about these applications, please visit the pages linked below.<br />
*[[GSFIT Help]]<br />
*[[GSFITCP Help]]<br />
*[[GSFITVIEW Help]]<br />
<br />
Platform specific installation instructions for the GSFIT package are provided on this page.<br />
<br />
=GSFIT Linux / Mac OS Requirements=<br />
On Mac and Unix platforms, the gfortran compiler must be also installed to allow automatic compilation of the source code located in the ..//gsfit/unix directory, in order to generate a series of shared libraries, when gsfit is launched for the first time. WARNING: For this action to be successfully completed, the user must have writing rights to the ..//gsfit/unix directory.<br />
<br />
=GSFIT Windows OS Requirements=<br />
The GSFIT package is distributed along with a set of dynamic link libraries located in the ..//gsfit/win subfolder, which have been compiled assuming a WIN64 architecture. For Win32, please contact us to inquire about alternative options.<br />
<br />
=GSFIT SSW_UPGRADE Installation=<br />
The release version of the IDL GSFIT package is intended to be distributed through the SSW IDL repository [https://www.lmsal.com/solarsoft/]. <br />
Although installed as a stand-alone package, the GSFIT code relies on a series of IDL support routines that are part of the gx_simulator package. Therefore, in addition to installing the gsfit package , the gx_simulator package must be also installed. This installation can be performed by issuing an upgrade command, i.e.<br />
<br />
<pre><br />
IDL> ssw_upgrade,/gsfit,/gx_simulator,/gen,/spawn,/loud,/passive_ftp <br />
</pre><br />
<br />
=GSFIT SSW Instrument Setup=<br />
After the SSW installation is upgraded to include gsfit and gx_simulator packages, to ensure proper functionality, one should also edit the sswidl.bat (on Windows platforms) or cshrc (on Unix or Mac platforms) scripts to include gx_simulator and gsfit in the SSW_INSTR path declaration, i.e.<br />
<pre><br />
set SSW_INSTR=gx_simulator, gsfit [...] <br />
</pre><br />
where [..] denotes any other SSW packages already installed.<br />
<br />
=GSFIT Manual Stand-Alone Installation=<br />
Although '''not reccomended''', one may in principle choose to install the gsfit and gx_simulator packages in standalone directories that are not part of the SSW repositories. However if this (not recommended) option is used, the gsfit and gx_simulator paths should be explicitly added to the IDL !path global variable, i.e. <br />
<br />
and explicitly add this path to your IDL path structure.<br />
<br />
<pre><br />
IDL> !path='..//gsfit/idl:'+!path<br />
IDL> !path='..//gx_simulator/idl:'+!path<br />
</pre><br />
<br />
where '''../''' should be replaced with the explicit paths to the respective local machine repositories.</div>Gnitahttp://ovsa.njit.edu//wiki/index.php?title=GSFIT_Installation&diff=4220GSFIT Installation2019-05-18T21:44:15Z<p>Gnita: /* GSFIT Manual SWW Installation and Setup */</p>
<hr />
<div>[https://github.com/Gelu-Nita/GSFIT GSFIT] is an IDL-widget(GUI)-based spectral fitting package that provides a user-friendly display of [http://www.ovsa.njit.edu/ EOVSA] image cubes and an interface to fast fitting codes (via platform-dependent shared-object libraries). Fits to individual spectra can be done quickly for manual investigation using a GUI application called [http://www.ovsa.njit.edu/wiki/index.php/GSFIT_Help GSFIT], while parallel/multi-core batch processing of selected blocks of data can also be performed using a command prompt application called [http://www.ovsa.njit.edu/wiki/index.php/GSFITCP_Help GSFITCP]. A helper routine called [http://www.ovsa.njit.edu/wiki/index.php/GSFITVIEW_Help GSFITVIEW] allows further display and investigation of the fitting results.<br />
For detailed information about these applications, please visit the pages linked below.<br />
*[[GSFIT Help]]<br />
*[[GSFITCP Help]]<br />
*[[GSFITVIEW Help]]<br />
<br />
Platform specific installation instructions for the GSFIT package are provided on this page.<br />
<br />
=GSFIT Linux / Mac OS Requirements=<br />
On Mac and Unix platforms, the gfortran compiler must be also installed to allow automatic compilation of the source code located in the ..//gsfit/unix directory, in order to generate a series of shared libraries, when gsfit is launched for the first time. WARNING: For this action to be successfully completed, the user must have writing rights to the ..//gsfit/unix directory.<br />
<br />
=GSFIT Windows OS Requirements=<br />
The GSFIT package is distributed along with a set of dynamic link libraries located in the ..//gsfit/win subfolder, which have been compiled assuming a WIN64 architecture. For Win32, please contact us to inquire about alternative options.<br />
<br />
=GSFIT SSW_UPGRADE Installation=<br />
The release version of the IDL GSFIT package is intended to be distributed through the SSW IDL repository [https://www.lmsal.com/solarsoft/]. <br />
Although installed as a stand-alone package, the GSFIT code relies on a series of IDL support routines that are part of the gx_simulator package. Therefore, in addition to installing the gsfit package , the gx_simulator package must be also installed. This installation can be performed by issuing an upgrade command, i.e.<br />
<br />
<pre><br />
IDL> ssw_upgrade,/gsfit,/gx_simulator,/gen,/spawn,/loud,/passive_ftp <br />
</pre><br />
<br />
=GSFIT SSW Instrument Setup=<br />
Please note that, regardless the method chosen to install any of these two packages, to ensure proper functionality, one should make sure that sswidl.bat (on Windows platforms) or cshrc (on Unix or Mac platforms) scripts are properly updated such as to include gx_simulator and gsfit in the SSW_INSTR path declaration, i.e.<br />
<pre><br />
set SSW_INSTR=gx_simulator, gsfit [...] <br />
</pre><br />
where [..] denotes any other SSW packages already installed.<br />
<br />
=GSFIT Manual Stand-Alone Installation=<br />
Although '''not reccomended''', one may in principle choose to install the gsfit and gx_simulator packages in standalone directories that are not part of the SSW repositories. However if this (not recommended) option is used, the gsfit and gx_simulator paths should be explicitly added to the IDL !path global variable, i.e. <br />
<br />
and explicitly add this path to your IDL path structure.<br />
<br />
<pre><br />
IDL> !path='..//gsfit/idl:'+!path<br />
IDL> !path='..//gx_simulator/idl:'+!path<br />
</pre><br />
<br />
where '''../''' should be replaced with the explicit paths to the respective local machine repositories.</div>Gnitahttp://ovsa.njit.edu//wiki/index.php?title=GSFIT_Installation&diff=4219GSFIT Installation2019-05-18T21:43:22Z<p>Gnita: /* GSFIT Manual SWW Installation and Setup */</p>
<hr />
<div>[https://github.com/Gelu-Nita/GSFIT GSFIT] is an IDL-widget(GUI)-based spectral fitting package that provides a user-friendly display of [http://www.ovsa.njit.edu/ EOVSA] image cubes and an interface to fast fitting codes (via platform-dependent shared-object libraries). Fits to individual spectra can be done quickly for manual investigation using a GUI application called [http://www.ovsa.njit.edu/wiki/index.php/GSFIT_Help GSFIT], while parallel/multi-core batch processing of selected blocks of data can also be performed using a command prompt application called [http://www.ovsa.njit.edu/wiki/index.php/GSFITCP_Help GSFITCP]. A helper routine called [http://www.ovsa.njit.edu/wiki/index.php/GSFITVIEW_Help GSFITVIEW] allows further display and investigation of the fitting results.<br />
For detailed information about these applications, please visit the pages linked below.<br />
*[[GSFIT Help]]<br />
*[[GSFITCP Help]]<br />
*[[GSFITVIEW Help]]<br />
<br />
Platform specific installation instructions for the GSFIT package are provided on this page.<br />
<br />
=GSFIT Linux / Mac OS Requirements=<br />
On Mac and Unix platforms, the gfortran compiler must be also installed to allow automatic compilation of the source code located in the ..//gsfit/unix directory, in order to generate a series of shared libraries, when gsfit is launched for the first time. WARNING: For this action to be successfully completed, the user must have writing rights to the ..//gsfit/unix directory.<br />
<br />
=GSFIT Windows OS Requirements=<br />
The GSFIT package is distributed along with a set of dynamic link libraries located in the ..//gsfit/win subfolder, which have been compiled assuming a WIN64 architecture. For Win32, please contact us to inquire about alternative options.<br />
<br />
=GSFIT SSW_UPGRADE Installation=<br />
The release version of the IDL GSFIT package is intended to be distributed through the SSW IDL repository [https://www.lmsal.com/solarsoft/]. <br />
Although installed as a stand-alone package, the GSFIT code relies on a series of IDL support routines that are part of the gx_simulator package. Therefore, in addition to installing the gsfit package , the gx_simulator package must be also installed. This installation can be performed by issuing an upgrade command, i.e.<br />
<br />
<pre><br />
IDL> ssw_upgrade,/gsfit,/gx_simulator,/gen,/spawn,/loud,/passive_ftp <br />
</pre><br />
<br />
=GSFIT Manual SWW Installation and Setup=<br />
Although not recommended, one may perform a manual installation of the GSFIT package by copying the directory structure located at https://github.com/Gelu-Nita/GSFIT to your local machine SSW directory, $ssw/packages/gsfit/' <br />
However, if such manual installation is performed, the $ssw/gen/setup/setup.ssw_env script must be edited by adding or altering the following lines:<br />
<pre><br />
setenv SSW_GSFIT $SSW_PACKAGES/gsfit<br />
<br />
setenv SSW_PACKAGES_INSTR "packages/gsfit [...]"<br />
<br />
setenv SSW_PACKAGES_ALL "$SSW_GSFIT [...]"<br />
</pre><br />
<br />
where [...] denote the definitions already existent in the original setup.ssw_env script.<br />
<br />
=GSFIT SSW Instrument Setup=<br />
Please note that, regardless the method chosen to install any of these two packages, to ensure proper functionality, one should make sure that sswidl.bat (on Windows platforms) or cshrc (on Unix or Mac platforms) scripts are properly updated such as to include gx_simulator and gsfit in the SSW_INSTR path declaration, i.e.<br />
<pre><br />
set SSW_INSTR=gx_simulator, gsfit [...] <br />
</pre><br />
where [..] denotes any other SSW packages already installed.<br />
<br />
=GSFIT Manual Stand-Alone Installation=<br />
Although '''not reccomended''', one may in principle choose to install the gsfit and gx_simulator packages in standalone directories that are not part of the SSW repositories. However if this (not recommended) option is used, the gsfit and gx_simulator paths should be explicitly added to the IDL !path global variable, i.e. <br />
<br />
and explicitly add this path to your IDL path structure.<br />
<br />
<pre><br />
IDL> !path='..//gsfit/idl:'+!path<br />
IDL> !path='..//gx_simulator/idl:'+!path<br />
</pre><br />
<br />
where '''../''' should be replaced with the explicit paths to the respective local machine repositories.</div>Gnitahttp://ovsa.njit.edu//wiki/index.php?title=GSFIT_Installation&diff=4177GSFIT Installation2019-05-17T19:33:12Z<p>Gnita: /* GSFIT Manual SWW Installation and Setup */</p>
<hr />
<div>[https://github.com/Gelu-Nita/GSFIT GSFIT] is an IDL-widget(GUI)-based spectral fitting package that provides a user-friendly display of [http://www.ovsa.njit.edu/ EOVSA] image cubes and an interface to fast fitting codes (via platform-dependent shared-object libraries). Fits to individual spectra can be done quickly for manual investigation using a GUI application called [http://www.ovsa.njit.edu/wiki/index.php/GSFIT_Help GSFIT], while parallel/multi-core batch processing of selected blocks of data can also be performed using a command prompt application called [http://www.ovsa.njit.edu/wiki/index.php/GSFITCP_Help GSFITCP]. A helper routine called [http://www.ovsa.njit.edu/wiki/index.php/GSFITVIEW_Help GSFITVIEW] allows further display and investigation of the fitting results.<br />
For detailed information about these applications, please visit the pages linked below.<br />
*[[GSFIT Help]]<br />
*[[GSFITCP Help]]<br />
*[[GSFITVIEW Help]]<br />
<br />
Platform specific installation instructions for the GSFIT package are provided on this page.<br />
<br />
=GSFIT Linux / Mac OS Requirements=<br />
On Mac and Unix platforms, the gfortran compiler must be also installed to allow automatic compilation of the source code located in the ..//gsfit/unix directory, in order to generate a series of shared libraries, when gsfit is launched for the first time. WARNING: For this action to be successfully completed, the user must have writing rights to the ..//gsfit/unix directory.<br />
<br />
=GSFIT Windows OS Requirements=<br />
The GSFIT package is distributed along with a set of dynamic link libraries located in the ..//gsfit/win subfolder, which have been compiled assuming a WIN64 architecture. For Win32, please contact us to inquire about alternative options.<br />
<br />
=GSFIT SSW_UPGRADE Installation=<br />
The release version of the IDL GSFIT package is intended to be distributed through the SSW IDL repository [https://www.lmsal.com/solarsoft/]. <br />
Although installed as a stand-alone package, the GSFIT code relies on a series of IDL support routines that are part of the gx_simulator package. Therefore, in addition to installing the gsfit package , the gx_simulator package must be also installed. This installation can be performed by issuing an upgrade command, i.e.<br />
<br />
<pre><br />
IDL> ssw_upgrade,/gsfit,/gx_simulator,/gen,/spawn,/loud,/passive_ftp <br />
</pre><br />
<br />
=GSFIT Manual SWW Installation and Setup=<br />
However, if as of today the GSFIT package has not been yet released through SSW, you may perform a manual install by copying the directory structure located at https://github.com/Gelu-Nita/GSFIT to your local machine SSW directory, $ssw/packages/gsfit/' <br />
If such manual installation is performed, the $ssw/gen/setup/setup.ssw_env script must be edited by adding or altering the following lines:<br />
<pre><br />
setenv SSW_GSFIT $SSW_PACKAGES/gsfit<br />
<br />
setenv SSW_PACKAGES_INSTR "packages/gsfit [...]"<br />
<br />
setenv SSW_PACKAGES_ALL "$SSW_GSFIT [...]"<br />
</pre><br />
<br />
where [...] denote the definitions already existent in the original setup.ssw_env script.<br />
<br />
=GSFIT SSW Instrument Setup=<br />
Please note that, regardless the method chosen to install any of these two packages, to ensure proper functionality, one should make sure that sswidl.bat (on Windows platforms) or cshrc (on Unix or Mac platforms) scripts are properly updated such as to include gx_simulator and gsfit in the SSW_INSTR path declaration, i.e.<br />
<pre><br />
set SSW_INSTR=gx_simulator, gsfit [...] <br />
</pre><br />
where [..] denotes any other SSW packages already installed.<br />
<br />
=GSFIT Manual Stand-Alone Installation=<br />
Although '''not reccomended''', one may in principle choose to install the gsfit and gx_simulator packages in standalone directories that are not part of the SSW repositories. However if this (not recommended) option is used, the gsfit and gx_simulator paths should be explicitly added to the IDL !path global variable, i.e. <br />
<br />
and explicitly add this path to your IDL path structure.<br />
<br />
<pre><br />
IDL> !path='..//gsfit/idl:'+!path<br />
IDL> !path='..//gx_simulator/idl:'+!path<br />
</pre><br />
<br />
where '''../''' should be replaced with the explicit paths to the respective local machine repositories.</div>Gnitahttp://ovsa.njit.edu//wiki/index.php?title=GSFITCP_Help&diff=3955GSFITCP Help2019-05-14T17:45:07Z<p>Gnita: /* Command line or programmatic manipulation of the GSFITCP results */</p>
<hr />
<div>GSFITCP is the command prompt counterpart of the GSFIT GUI microwave spectral fitting application. Once started, GSFITCP is designed to run in unattended mode until all fitting tasks assigned to it are completed and log on the disk in an user-defined *.log file, the content of which may be visualized using the GSFITVIEW GUI application. When run remotely on an Linux/Mac platform, the GSFITCP may be launched on a detached [https://linuxize.com/post/how-to-use-linux-screen/ screen], which allows the remote user to logout without stopping the process in which GSFITCP runs.<br />
<br />
=GSFITCP Installation=<br />
GSFITCP is part of the GSFIT IDL Package<br />
<br />
To get installation instructions for the IDL GSFIT package, please visit the [[GSFIT Installation]] page.<br />
<br />
=Launching the GSFITCP command prompt application=<br />
<br />
To obtain a list of valid GSFIT calling sequences one may call '''''gsfitcp''''' with no arguments:<br />
<pre><br />
IDL> gsfitcp<br />
% GSFITCP: For a detailed description visit http://www.ovsa.njit.edu/wiki/index.php/GSFITCP_Help, or use one of the folowing calling sequences:<br />
% IDL-> gsfitcp, taskfilename; to provide a path to a stored GSFIT task stracture<br />
% IDL-> gsfitcp, taskstructure; to provide an already restored GSFIT task structure<br />
% IDL-> gsfitcp, nthreads; to set,increase, or decrease the number of ashyncronious threads to be used<br />
% IDL-> gsfitcp, out=out,log; to change the default "gsfitcp.log" path for run-time logging of the results.<br />
% IDL-> gsfitcp, /status; to report the status of the application<br />
% IDL-> gsfitcp, /quiet; to inhibit automatic printing of progress report messages at run-time<br />
% IDL-> gsfitcp, /start; to start processing the task queue<br />
% IDL-> gsfitcp, /flush; to flush the pending task queue<br />
% IDL-> gsfitcp, /abort; to abort all active tasks and flush the pending task queue<br />
% IDL-> gsfitcp, /exit; to abort all active tasks, flush the pending task queue, and exit the apllication<br />
% GSFITCP: % Any logical combination of the arguments and keywords listed above should result in a valid single-line calling sequence<br />
</pre><br />
NOTE: GSFITCP processes all fittings task in at least one asynchronous parallel thread. Therefore, the IDL command line should remain active for other tasks while GSFITCP is running in the background. However, to avoid any clashes with automatic progress report messages printed by GSFIT at the IDL console any time a parallel thread returns a result, the '''''IDL-> gsfitcp, /quiet''''' command may be issued at any time. Use '''''IDL-> gsfitcp, quiet=0''''' to turn these run-time messages back on. <br />
=Visualizing the GSFITCP results=<br />
==Visualizing the GSFITCP results using the GSFITVIEW GUI application==<br />
While processing its fit task queue, GSFITCP continuously logs the individual pixel-based solutions, as they are returned by the parallel thread to which they are assigned. The default GSFITCP log file, called '''''gsfitcp.log''''' is located in the local directory. However, the user may set a different log file using the command <br />
<pre><br />
IDL-> gsfitcp, out=out<br />
</pre><br />
where out is any valid file path.<br />
<br />
To visualize the final or partial fit results at any time, even while '''''gsfitcp''''' is still running in the background use<br />
<pre><br />
IDL> gsfitview, 'cplog' <br />
</pre><br />
<br />
Visit the [[GSFITVIEW Help]] page for detailed information about GSFITVIEW GUI functionality.<br />
<br />
==Command line or programmatic manipulation of the GSFITCP results==<br />
The GSFIT package provides a support routine that my be used to restore and convert the GSFITCP fit results to a GSFIT Parameter Maps IDL structure that may be inspected and manipulated at the command line or programmatically.<br />
<br />
<pre><br />
map=gsfit_log2map('gsfitcp.log')<br />
</pre><br />
<br />
Visit [[GSFIT Data Format]] for detailed information about this data structure.</div>Gnitahttp://ovsa.njit.edu//wiki/index.php?title=GSFITCP_Help&diff=3950GSFITCP Help2019-05-14T17:40:06Z<p>Gnita: /* Visualizing GSFITCP results using the GSFITVIEW GUI application */</p>
<hr />
<div>GSFITCP is the command prompt counterpart of the GSFIT GUI microwave spectral fitting application. Once started, GSFITCP is designed to run in unattended mode until all fitting tasks assigned to it are completed and log on the disk in an user-defined *.log file, the content of which may be visualized using the GSFITVIEW GUI application. When run remotely on an Linux/Mac platform, the GSFITCP may be launched on a detached [https://linuxize.com/post/how-to-use-linux-screen/ screen], which allows the remote user to logout without stopping the process in which GSFITCP runs.<br />
<br />
=GSFITCP Installation=<br />
GSFITCP is part of the GSFIT IDL Package<br />
<br />
To get installation instructions for the IDL GSFIT package, please visit the [[GSFIT Installation]] page.<br />
<br />
=Launching the GSFITCP command prompt application=<br />
<br />
To obtain a list of valid GSFIT calling sequences one may call '''''gsfitcp''''' with no arguments:<br />
<pre><br />
IDL> gsfitcp<br />
% GSFITCP: For a detailed description visit http://www.ovsa.njit.edu/wiki/index.php/GSFITCP_Help, or use one of the folowing calling sequences:<br />
% IDL-> gsfitcp, taskfilename; to provide a path to a stored GSFIT task stracture<br />
% IDL-> gsfitcp, taskstructure; to provide an already restored GSFIT task structure<br />
% IDL-> gsfitcp, nthreads; to set,increase, or decrease the number of ashyncronious threads to be used<br />
% IDL-> gsfitcp, out=out,log; to change the default "gsfitcp.log" path for run-time logging of the results.<br />
% IDL-> gsfitcp, /status; to report the status of the application<br />
% IDL-> gsfitcp, /quiet; to inhibit automatic printing of progress report messages at run-time<br />
% IDL-> gsfitcp, /start; to start processing the task queue<br />
% IDL-> gsfitcp, /flush; to flush the pending task queue<br />
% IDL-> gsfitcp, /abort; to abort all active tasks and flush the pending task queue<br />
% IDL-> gsfitcp, /exit; to abort all active tasks, flush the pending task queue, and exit the apllication<br />
% GSFITCP: % Any logical combination of the arguments and keywords listed above should result in a valid single-line calling sequence<br />
</pre><br />
NOTE: GSFITCP processes all fittings task in at least one asynchronous parallel thread. Therefore, the IDL command line should remain active for other tasks while GSFITCP is running in the background. However, to avoid any clashes with automatic progress report messages printed by GSFIT at the IDL console any time a parallel thread returns a result, the '''''IDL-> gsfitcp, /quiet''''' command may be issued at any time. Use '''''IDL-> gsfitcp, quiet=0''''' to turn these run-time messages back on. <br />
=Visualizing the GSFITCP results=<br />
==Visualizing the GSFITCP results using the GSFITVIEW GUI application==<br />
While processing its fit task queue, GSFITCP continuously logs the individual pixel-based solutions, as they are returned by the parallel thread to which they are assigned. The default GSFITCP log file, called '''''gsfitcp.log''''' is located in the local directory. However, the user may set a different log file using the command <br />
<pre><br />
IDL-> gsfitcp, out=out<br />
</pre><br />
where out is any valid file path.<br />
<br />
To visualize the final or partial fit results at any time, even while '''''gsfitcp''''' is still running in the background use<br />
<pre><br />
IDL> gsfitview, 'cplog' <br />
</pre><br />
<br />
Visit the [[GSFITVIEW Help]] page for detailed information about GSFITVIEW GUI functionality.<br />
<br />
==Command line or programmatic manipulation of the GSFITCP results==</div>Gnitahttp://ovsa.njit.edu//wiki/index.php?title=GSFITCP_Help&diff=3949GSFITCP Help2019-05-14T17:38:52Z<p>Gnita: /* Visualizing GSFITCP results using the GSFITVIEW GUI application */</p>
<hr />
<div>GSFITCP is the command prompt counterpart of the GSFIT GUI microwave spectral fitting application. Once started, GSFITCP is designed to run in unattended mode until all fitting tasks assigned to it are completed and log on the disk in an user-defined *.log file, the content of which may be visualized using the GSFITVIEW GUI application. When run remotely on an Linux/Mac platform, the GSFITCP may be launched on a detached [https://linuxize.com/post/how-to-use-linux-screen/ screen], which allows the remote user to logout without stopping the process in which GSFITCP runs.<br />
<br />
=GSFITCP Installation=<br />
GSFITCP is part of the GSFIT IDL Package<br />
<br />
To get installation instructions for the IDL GSFIT package, please visit the [[GSFIT Installation]] page.<br />
<br />
=Launching the GSFITCP command prompt application=<br />
<br />
To obtain a list of valid GSFIT calling sequences one may call '''''gsfitcp''''' with no arguments:<br />
<pre><br />
IDL> gsfitcp<br />
% GSFITCP: For a detailed description visit http://www.ovsa.njit.edu/wiki/index.php/GSFITCP_Help, or use one of the folowing calling sequences:<br />
% IDL-> gsfitcp, taskfilename; to provide a path to a stored GSFIT task stracture<br />
% IDL-> gsfitcp, taskstructure; to provide an already restored GSFIT task structure<br />
% IDL-> gsfitcp, nthreads; to set,increase, or decrease the number of ashyncronious threads to be used<br />
% IDL-> gsfitcp, out=out,log; to change the default "gsfitcp.log" path for run-time logging of the results.<br />
% IDL-> gsfitcp, /status; to report the status of the application<br />
% IDL-> gsfitcp, /quiet; to inhibit automatic printing of progress report messages at run-time<br />
% IDL-> gsfitcp, /start; to start processing the task queue<br />
% IDL-> gsfitcp, /flush; to flush the pending task queue<br />
% IDL-> gsfitcp, /abort; to abort all active tasks and flush the pending task queue<br />
% IDL-> gsfitcp, /exit; to abort all active tasks, flush the pending task queue, and exit the apllication<br />
% GSFITCP: % Any logical combination of the arguments and keywords listed above should result in a valid single-line calling sequence<br />
</pre><br />
NOTE: GSFITCP processes all fittings task in at least one asynchronous parallel thread. Therefore, the IDL command line should remain active for other tasks while GSFITCP is running in the background. However, to avoid any clashes with automatic progress report messages printed by GSFIT at the IDL console any time a parallel thread returns a result, the '''''IDL-> gsfitcp, /quiet''''' command may be issued at any time. Use '''''IDL-> gsfitcp, quiet=0''''' to turn these run-time messages back on. <br />
=Visualizing the GSFITCP results=<br />
==Visualizing GSFITCP results using the GSFITVIEW GUI application==<br />
While processing its fit task queue, GSFITCP continuously logs the individual pixel-based solutions, as they are returned by the parallel thread to which they are assigned. The default GSFITCP log file, called '''''gsfitcp.log''''' is located in the local directory. However, the user may set a different log file using the command <br />
<pre>IDL-> gsfitcp, out=out</pre><br />
where out is any valid file path.<br />
<br />
To visualize the final or partial fit results at any time, even while '''''gsfitcp''''' is still running in the background use<br />
<pre><br />
IDL> gsfitview, 'cplog' <br />
</pre><br />
<br />
Visit the [[GSFITVIEW Help]] page for detailed information about GSFITVIEW GUI functionality.</div>Gnitahttp://ovsa.njit.edu//wiki/index.php?title=GSFITCP_Help&diff=3947GSFITCP Help2019-05-14T17:38:24Z<p>Gnita: /* Visualizing GSFITCP results using the GSFITVIEW GUI application */</p>
<hr />
<div>GSFITCP is the command prompt counterpart of the GSFIT GUI microwave spectral fitting application. Once started, GSFITCP is designed to run in unattended mode until all fitting tasks assigned to it are completed and log on the disk in an user-defined *.log file, the content of which may be visualized using the GSFITVIEW GUI application. When run remotely on an Linux/Mac platform, the GSFITCP may be launched on a detached [https://linuxize.com/post/how-to-use-linux-screen/ screen], which allows the remote user to logout without stopping the process in which GSFITCP runs.<br />
<br />
=GSFITCP Installation=<br />
GSFITCP is part of the GSFIT IDL Package<br />
<br />
To get installation instructions for the IDL GSFIT package, please visit the [[GSFIT Installation]] page.<br />
<br />
=Launching the GSFITCP command prompt application=<br />
<br />
To obtain a list of valid GSFIT calling sequences one may call '''''gsfitcp''''' with no arguments:<br />
<pre><br />
IDL> gsfitcp<br />
% GSFITCP: For a detailed description visit http://www.ovsa.njit.edu/wiki/index.php/GSFITCP_Help, or use one of the folowing calling sequences:<br />
% IDL-> gsfitcp, taskfilename; to provide a path to a stored GSFIT task stracture<br />
% IDL-> gsfitcp, taskstructure; to provide an already restored GSFIT task structure<br />
% IDL-> gsfitcp, nthreads; to set,increase, or decrease the number of ashyncronious threads to be used<br />
% IDL-> gsfitcp, out=out,log; to change the default "gsfitcp.log" path for run-time logging of the results.<br />
% IDL-> gsfitcp, /status; to report the status of the application<br />
% IDL-> gsfitcp, /quiet; to inhibit automatic printing of progress report messages at run-time<br />
% IDL-> gsfitcp, /start; to start processing the task queue<br />
% IDL-> gsfitcp, /flush; to flush the pending task queue<br />
% IDL-> gsfitcp, /abort; to abort all active tasks and flush the pending task queue<br />
% IDL-> gsfitcp, /exit; to abort all active tasks, flush the pending task queue, and exit the apllication<br />
% GSFITCP: % Any logical combination of the arguments and keywords listed above should result in a valid single-line calling sequence<br />
</pre><br />
NOTE: GSFITCP processes all fittings task in at least one asynchronous parallel thread. Therefore, the IDL command line should remain active for other tasks while GSFITCP is running in the background. However, to avoid any clashes with automatic progress report messages printed by GSFIT at the IDL console any time a parallel thread returns a result, the '''''IDL-> gsfitcp, /quiet''''' command may be issued at any time. Use '''''IDL-> gsfitcp, quiet=0''''' to turn these run-time messages back on. <br />
=Visualizing the GSFITCP results=<br />
==Visualizing GSFITCP results using the GSFITVIEW GUI application==<br />
While processing its fit task queue, GSFITCP continuously logs the individual pixel-based solutions, as they are returned by the parallel thread to which they are assigned. The default GSFITCP log file, called '''''gsfitcp.log''''' is located in the local directory. However, the user may set a different log file using the command <pre>IDL-> gsfitcp, out=out</pre>, where out is any valid file path.<br />
<br />
To visualize the final or partial fit results at any time, even while '''''gsfitcp''''' is still running in the background use<br />
<pre><br />
IDL> gsfitview, 'cplog' <br />
</pre><br />
<br />
Visit the [[GSFITVIEW Help]] page for detailed information about GSFITVIEW GUI functionality.</div>Gnitahttp://ovsa.njit.edu//wiki/index.php?title=GSFITCP_Help&diff=3945GSFITCP Help2019-05-14T17:37:43Z<p>Gnita: /* Visualizing the GSFITCP results */</p>
<hr />
<div>GSFITCP is the command prompt counterpart of the GSFIT GUI microwave spectral fitting application. Once started, GSFITCP is designed to run in unattended mode until all fitting tasks assigned to it are completed and log on the disk in an user-defined *.log file, the content of which may be visualized using the GSFITVIEW GUI application. When run remotely on an Linux/Mac platform, the GSFITCP may be launched on a detached [https://linuxize.com/post/how-to-use-linux-screen/ screen], which allows the remote user to logout without stopping the process in which GSFITCP runs.<br />
<br />
=GSFITCP Installation=<br />
GSFITCP is part of the GSFIT IDL Package<br />
<br />
To get installation instructions for the IDL GSFIT package, please visit the [[GSFIT Installation]] page.<br />
<br />
=Launching the GSFITCP command prompt application=<br />
<br />
To obtain a list of valid GSFIT calling sequences one may call '''''gsfitcp''''' with no arguments:<br />
<pre><br />
IDL> gsfitcp<br />
% GSFITCP: For a detailed description visit http://www.ovsa.njit.edu/wiki/index.php/GSFITCP_Help, or use one of the folowing calling sequences:<br />
% IDL-> gsfitcp, taskfilename; to provide a path to a stored GSFIT task stracture<br />
% IDL-> gsfitcp, taskstructure; to provide an already restored GSFIT task structure<br />
% IDL-> gsfitcp, nthreads; to set,increase, or decrease the number of ashyncronious threads to be used<br />
% IDL-> gsfitcp, out=out,log; to change the default "gsfitcp.log" path for run-time logging of the results.<br />
% IDL-> gsfitcp, /status; to report the status of the application<br />
% IDL-> gsfitcp, /quiet; to inhibit automatic printing of progress report messages at run-time<br />
% IDL-> gsfitcp, /start; to start processing the task queue<br />
% IDL-> gsfitcp, /flush; to flush the pending task queue<br />
% IDL-> gsfitcp, /abort; to abort all active tasks and flush the pending task queue<br />
% IDL-> gsfitcp, /exit; to abort all active tasks, flush the pending task queue, and exit the apllication<br />
% GSFITCP: % Any logical combination of the arguments and keywords listed above should result in a valid single-line calling sequence<br />
</pre><br />
NOTE: GSFITCP processes all fittings task in at least one asynchronous parallel thread. Therefore, the IDL command line should remain active for other tasks while GSFITCP is running in the background. However, to avoid any clashes with automatic progress report messages printed by GSFIT at the IDL console any time a parallel thread returns a result, the '''''IDL-> gsfitcp, /quiet''''' command may be issued at any time. Use '''''IDL-> gsfitcp, quiet=0''''' to turn these run-time messages back on. <br />
=Visualizing the GSFITCP results=<br />
==Visualizing GSFITCP results using the GSFITVIEW GUI application==<br />
While processing its fit task queue, GSFITCP continuously logs the individual pixel-based solutions, as they are returned by the parallel thread to which they are assigned. The default GSFITCP log file, called '''''gsfitcp.log''''' is located in the local directory. However, the user may set a different log file using the command IDL-> gsfitcp, out=out'''''', where out is any valid file path.<br />
<br />
To visualize the final or partial fit results at any time, even while '''''gsfitcp''''' is still running in the background use<br />
<pre><br />
IDL> gsfitview, 'cplog' <br />
</pre><br />
<br />
Visit the [[GSFITVIEW Help]] page for detailed information about GSFITVIEW GUI functionality.</div>Gnitahttp://ovsa.njit.edu//wiki/index.php?title=GSFITCP_Help&diff=3940GSFITCP Help2019-05-14T17:28:18Z<p>Gnita: </p>
<hr />
<div>GSFITCP is the command prompt counterpart of the GSFIT GUI microwave spectral fitting application. Once started, GSFITCP is designed to run in unattended mode until all fitting tasks assigned to it are completed and log on the disk in an user-defined *.log file, the content of which may be visualized using the GSFITVIEW GUI application. When run remotely on an Linux/Mac platform, the GSFITCP may be launched on a detached [https://linuxize.com/post/how-to-use-linux-screen/ screen], which allows the remote user to logout without stopping the process in which GSFITCP runs.<br />
<br />
=GSFITCP Installation=<br />
GSFITCP is part of the GSFIT IDL Package<br />
<br />
To get installation instructions for the IDL GSFIT package, please visit the [[GSFIT Installation]] page.<br />
<br />
=Launching the GSFITCP command prompt application=<br />
<br />
To obtain a list of valid GSFIT calling sequences one may call '''''gsfitcp''''' with no arguments:<br />
<pre><br />
IDL> gsfitcp<br />
% GSFITCP: For a detailed description visit http://www.ovsa.njit.edu/wiki/index.php/GSFITCP_Help, or use one of the folowing calling sequences:<br />
% IDL-> gsfitcp, taskfilename; to provide a path to a stored GSFIT task stracture<br />
% IDL-> gsfitcp, taskstructure; to provide an already restored GSFIT task structure<br />
% IDL-> gsfitcp, nthreads; to set,increase, or decrease the number of ashyncronious threads to be used<br />
% IDL-> gsfitcp, out=out,log; to change the default "gsfitcp.log" path for run-time logging of the results.<br />
% IDL-> gsfitcp, /status; to report the status of the application<br />
% IDL-> gsfitcp, /quiet; to inhibit automatic printing of progress report messages at run-time<br />
% IDL-> gsfitcp, /start; to start processing the task queue<br />
% IDL-> gsfitcp, /flush; to flush the pending task queue<br />
% IDL-> gsfitcp, /abort; to abort all active tasks and flush the pending task queue<br />
% IDL-> gsfitcp, /exit; to abort all active tasks, flush the pending task queue, and exit the apllication<br />
% GSFITCP: % Any logical combination of the arguments and keywords listed above should result in a valid single-line calling sequence<br />
</pre><br />
NOTE: GSFITCP processes all fittings task in at least one asynchronous parallel thread. Therefore, the IDL command line should remain active for other tasks while GSFITCP is running in the background. However, to avoid any clashes with automatic progress report messages printed by GSFIT at the IDL console any time a parallel thread returns a result, the '''''IDL-> gsfitcp, /quiet''''' command may be issued at any time. Use '''''IDL-> gsfitcp, quiet=0''''' to turn these run-time messages back on. <br />
=Visualizing the GSFITCP results=</div>Gnitahttp://ovsa.njit.edu//wiki/index.php?title=GSFIT_Installation&diff=3939GSFIT Installation2019-05-14T16:02:37Z<p>Gnita: </p>
<hr />
<div>[https://github.com/Gelu-Nita/GSFIT GSFIT] is an IDL-widget(GUI)-based spectral fitting package that provides a user-friendly display of [http://www.ovsa.njit.edu/ EOVSA] image cubes and an interface to fast fitting codes (via platform-dependent shared-object libraries). Fits to individual spectra can be done quickly for manual investigation using a GUI application called [http://www.ovsa.njit.edu/wiki/index.php/GSFIT_Help GSFIT], while parallel/multi-core batch processing of selected blocks of data can also be performed using a command prompt application called [http://www.ovsa.njit.edu/wiki/index.php/GSFITCP_Help GSFITCP]. A helper routine called [http://www.ovsa.njit.edu/wiki/index.php/GSFITVIEW_Help GSFITVIEW] allows further display and investigation of the fitting results.<br />
For detailed information about these applications, please visit the pages linked below.<br />
*[[GSFIT Help]]<br />
*[[GSFITCP Help]]<br />
*[[GSFITVIEW Help]]<br />
<br />
Platform specific installation instructions for the GSFIT package are provided on this page.<br />
<br />
=GSFIT Linux / Mac OS Requirements=<br />
On Mac and Unix platforms, the gfortran compiler must be also installed to allow automatic compilation of the source code located in the ..//gsfit/unix directory, in order to generate a series of shared libraries, when gsfit is launched for the first time. WARNING: For this action to be successfully completed, the user must have writing rights to the ..//gsfit/unix directory.<br />
<br />
=GSFIT Windows OS Requirements=<br />
The GSFIT package is distributed along with a set of dynamic link libraries located in the ..//gsfit/win subfolder, which have been compiled assuming a WIN64 architecture. For Win32, please contact us to inquire about alternative options.<br />
<br />
=GSFIT SSW_UPGRADE Installation=<br />
The release version of the IDL GSFIT package is intended to be distributed through the SSW IDL repository [https://www.lmsal.com/solarsoft/]. <br />
Although installed as a stand-alone package, the GSFIT code relies on a series of IDL support routines that are part of the gx_simulator package. Therefore, in addition to installing the gsfit package , the gx_simulator package must be also installed. This installation can be performed by issuing an upgrade command, i.e.<br />
<br />
<pre><br />
IDL> ssw_upgrade,/gsfit,/gx_simulator,/gen,/spawn,/loud,/passive_ftp <br />
</pre><br />
<br />
=GSFIT Manual SWW Installation and Setup=<br />
However, if as of today the GSFIT package has not been yet released through SSW, you may perform a manual install by copying the directory structure located at https://github.com/Gelu-Nita/GSFIT to your local machine SSW directory, $ssw/packages/gsfit/' <br />
If such manual installation is performed, the $ssw/gen/setup/setup.ssw_env script must be edited by adding or altering the following lines:<br />
<pre><br />
setenv SSW_GSFIT $SSW_PACKAGES/gsfit$<br />
<br />
setenv SSW_PACKAGES_INSTR "packages/gsfit [...]"<br />
<br />
setenv SSW_PACKAGES_ALL "$SSW_GSFIT [...]"<br />
</pre><br />
<br />
where [...] denote the definitions already existent in the original setup.ssw_env script.<br />
<br />
=GSFIT SSW Instrument Setup=<br />
Please note that, regardless the method chosen to install any of these two packages, to ensure proper functionality, one should make sure that sswidl.bat (on Windows platforms) or cshrc (on Unix or Mac platforms) scripts are properly updated such as to include gx_simulator and gsfit in the SSW_INSTR path declaration, i.e.<br />
<pre><br />
set SSW_INSTR=gx_simulator, gsfit [...] <br />
</pre><br />
where [..] denotes any other SSW packages already installed.<br />
<br />
=GSFIT Manual Stand-Alone Installation=<br />
Although '''not reccomended''', one may in principle choose to install the gsfit and gx_simulator packages in standalone directories that are not part of the SSW repositories. However if this (not recommended) option is used, the gsfit and gx_simulator paths should be explicitly added to the IDL !path global variable, i.e. <br />
<br />
and explicitly add this path to your IDL path structure.<br />
<br />
<pre><br />
IDL> !path='..//gsfit/idl:'+!path<br />
IDL> !path='..//gx_simulator/idl:'+!path<br />
</pre><br />
<br />
where '''../''' should be replaced with the explicit paths to the respective local machine repositories.</div>Gnitahttp://ovsa.njit.edu//wiki/index.php?title=GSFIT_Installation&diff=3938GSFIT Installation2019-05-14T16:01:24Z<p>Gnita: </p>
<hr />
<div>[https://github.com/Gelu-Nita/GSFIT GSFIT] is an IDL-widget(GUI)-based spectral fitting package that provides a user-friendly display of [http://www.ovsa.njit.edu/ EOVSA] image cubes and an interface to fast fitting codes (via platform-dependent shared-object libraries). Fits to individual spectra can be done quickly for manual investigation using a GUI application called [http://www.ovsa.njit.edu/wiki/index.php/GSFIT_Help GSFIT], while parallel/multi-core batch processing of selected blocks of data can also be performed using a command prompt application called [http://www.ovsa.njit.edu/wiki/index.php/GSFITCP_Help GSFITCP]. A helper routine called [http://www.ovsa.njit.edu/wiki/index.php/GSFITVIEW_Help GSFITVIEW] allows further display and investigation of the fitting results.<br />
For detailed information about these applications, please visit the pages linked below.<br />
*[[GSFIT Help]]<br />
*[[GSFITCP Help]]<br />
*[[GSFITVIEW Help]]<br />
<br />
=GSFIT Linux / Mac OS Requirements=<br />
On Mac and Unix platforms, the gfortran compiler must be also installed to allow automatic compilation of the source code located in the ..//gsfit/unix directory, in order to generate a series of shared libraries, when gsfit is launched for the first time. WARNING: For this action to be successfully completed, the user must have writing rights to the ..//gsfit/unix directory.<br />
<br />
=GSFIT Windows OS Requirements=<br />
The GSFIT package is distributed along with a set of dynamic link libraries located in the ..//gsfit/win subfolder, which have been compiled assuming a WIN64 architecture. For Win32, please contact us to inquire about alternative options.<br />
<br />
=GSFIT SSW_UPGRADE Installation=<br />
The release version of the IDL GSFIT package is intended to be distributed through the SSW IDL repository [https://www.lmsal.com/solarsoft/]. <br />
Although installed as a stand-alone package, the GSFIT code relies on a series of IDL support routines that are part of the gx_simulator package. Therefore, in addition to installing the gsfit package , the gx_simulator package must be also installed. This installation can be performed by issuing an upgrade command, i.e.<br />
<br />
<pre><br />
IDL> ssw_upgrade,/gsfit,/gx_simulator,/gen,/spawn,/loud,/passive_ftp <br />
</pre><br />
<br />
=GSFIT Manual SWW Installation and Setup=<br />
However, if as of today the GSFIT package has not been yet released through SSW, you may perform a manual install by copying the directory structure located at https://github.com/Gelu-Nita/GSFIT to your local machine SSW directory, $ssw/packages/gsfit/' <br />
If such manual installation is performed, the $ssw/gen/setup/setup.ssw_env script must be edited by adding or altering the following lines:<br />
<pre><br />
setenv SSW_GSFIT $SSW_PACKAGES/gsfit$<br />
<br />
setenv SSW_PACKAGES_INSTR "packages/gsfit [...]"<br />
<br />
setenv SSW_PACKAGES_ALL "$SSW_GSFIT [...]"<br />
</pre><br />
<br />
where [...] denote the definitions already existent in the original setup.ssw_env script.<br />
<br />
=GSFIT SSW Instrument Setup=<br />
Please note that, regardless the method chosen to install any of these two packages, to ensure proper functionality, one should make sure that sswidl.bat (on Windows platforms) or cshrc (on Unix or Mac platforms) scripts are properly updated such as to include gx_simulator and gsfit in the SSW_INSTR path declaration, i.e.<br />
<pre><br />
set SSW_INSTR=gx_simulator, gsfit [...] <br />
</pre><br />
where [..] denotes any other SSW packages already installed.<br />
<br />
=GSFIT Manual Stand-Alone Installation=<br />
Although '''not reccomended''', one may in principle choose to install the gsfit and gx_simulator packages in standalone directories that are not part of the SSW repositories. However if this (not recommended) option is used, the gsfit and gx_simulator paths should be explicitly added to the IDL !path global variable, i.e. <br />
<br />
and explicitly add this path to your IDL path structure.<br />
<br />
<pre><br />
IDL> !path='..//gsfit/idl:'+!path<br />
IDL> !path='..//gx_simulator/idl:'+!path<br />
</pre><br />
<br />
where '''../''' should be replaced with the explicit paths to the respective local machine repositories.</div>Gnitahttp://ovsa.njit.edu//wiki/index.php?title=GSFIT_Installation&diff=3937GSFIT Installation2019-05-14T15:55:53Z<p>Gnita: </p>
<hr />
<div>[https://github.com/Gelu-Nita/GSFIT GSFIT] is an IDL-widget(GUI)-based spectral fitting package that provides a user-friendly display of [http://www.ovsa.njit.edu/ EOVSA] image cubes and an interface to fast fitting codes (via platform-dependent shared-object libraries). Fits to individual spectra can be done quickly for manual investigation using a GUI application called [http://www.ovsa.njit.edu/wiki/index.php/GSFIT_Help GSFIT], while parallel/multi-core batch processing of selected blocks of data can also be performed using a command prompt application called [http://www.ovsa.njit.edu/wiki/index.php/GSFITCP_Help GSFITCP]. A helper routine called [http://www.ovsa.njit.edu/wiki/index.php/GSFITVIEW_Help GSFITVIEW] allows further display and investigation of the fitting results.<br />
For detailed information about these applications, please visit the pages linked below.<br />
*[[GSFIT HELP]]<br />
*[[GSFITCP HELP]]<br />
*[[GSFITVIEW HELP]]<br />
<br />
=GSFIT Linux / Mac OS Requirements=<br />
On Mac and Unix platforms, the gfortran compiler must be also installed to allow automatic compilation of the source code located in the ..//gsfit/unix directory, in order to generate a series of shared libraries, when gsfit is launched for the first time. WARNING: For this action to be successfully completed, the user must have writing rights to the ..//gsfit/unix directory.<br />
<br />
=GSFIT Windows OS Requirements=<br />
The GSFIT package is distributed along with a set of dynamic link libraries located in the ..//gsfit/win subfolder, which have been compiled assuming a WIN64 architecture. For Win32, please contact us to inquire about alternative options.<br />
<br />
=GSFIT SSW_UPGRADE Installation=<br />
The release version of the IDL GSFIT package is intended to be distributed through the SSW IDL repository [https://www.lmsal.com/solarsoft/]. <br />
Although installed as a stand-alone package, the GSFIT code relies on a series of IDL support routines that are part of the gx_simulator package. Therefore, in addition to installing the gsfit package , the gx_simulator package must be also installed. This installation can be performed by issuing an upgrade command, i.e.<br />
<br />
<pre><br />
IDL> ssw_upgrade,/gsfit,/gx_simulator,/gen,/spawn,/loud,/passive_ftp <br />
</pre><br />
<br />
=GSFIT Manual SWW Installation and Setup=<br />
However, if as of today the GSFIT package has not been yet released through SSW, you may perform a manual install by copying the directory structure located at https://github.com/Gelu-Nita/GSFIT to your local machine SSW directory, $ssw/packages/gsfit/' <br />
If such manual installation is performed, the $ssw/gen/setup/setup.ssw_env script must be edited by adding or altering the following lines:<br />
<pre><br />
setenv SSW_GSFIT $SSW_PACKAGES/gsfit$<br />
<br />
setenv SSW_PACKAGES_INSTR "packages/gsfit [...]"<br />
<br />
setenv SSW_PACKAGES_ALL "$SSW_GSFIT [...]"<br />
</pre><br />
<br />
where [...] denote the definitions already existent in the original setup.ssw_env script.<br />
<br />
=GSFIT SSW Instrument Setup=<br />
Please note that, regardless the method chosen to install any of these two packages, to ensure proper functionality, one should make sure that sswidl.bat (on Windows platforms) or cshrc (on Unix or Mac platforms) scripts are properly updated such as to include gx_simulator and gsfit in the SSW_INSTR path declaration, i.e.<br />
<pre><br />
set SSW_INSTR=gx_simulator, gsfit [...] <br />
</pre><br />
where [..] denotes any other SSW packages already installed.<br />
<br />
=GSFIT Manual Stand-Alone Installation=<br />
Although '''not reccomended''', one may in principle choose to install the gsfit and gx_simulator packages in standalone directories that are not part of the SSW repositories. However if this (not recommended) option is used, the gsfit and gx_simulator paths should be explicitly added to the IDL !path global variable, i.e. <br />
<br />
and explicitly add this path to your IDL path structure.<br />
<br />
<pre><br />
IDL> !path='..//gsfit/idl:'+!path<br />
IDL> !path='..//gx_simulator/idl:'+!path<br />
</pre><br />
<br />
where '''../''' should be replaced with the explicit paths to the respective local machine repositories.</div>Gnitahttp://ovsa.njit.edu//wiki/index.php?title=GSFIT_Installation&diff=3936GSFIT Installation2019-05-14T15:55:33Z<p>Gnita: </p>
<hr />
<div>[https://github.com/Gelu-Nita/GSFIT GSFIT] is an IDL-widget(GUI)-based spectral fitting package that provides a user-friendly display of [http://www.ovsa.njit.edu/ EOVSA] image cubes and an interface to fast fitting codes (via platform-dependent shared-object libraries). Fits to individual spectra can be done quickly for manual investigation using a GUI application called [http://www.ovsa.njit.edu/wiki/index.php/GSFIT_Help GSFIT], while parallel/multi-core batch processing of selected blocks of data can also be performed using a command prompt application called [http://www.ovsa.njit.edu/wiki/index.php/GSFITCP_Help GSFITCP]. A helper routine called [http://www.ovsa.njit.edu/wiki/index.php/GSFITVIEW_Help GSFITVIEW] allows further display and investigation of the fitting results.<br />
For detailed information about these applications, please visit the pages linked below.<br />
*[[GSFIT HELP[]<br />
*[[GSFITCP HELP[]<br />
*[[GSFITVIEW HELP[]<br />
<br />
=GSFIT Linux / Mac OS Requirements=<br />
On Mac and Unix platforms, the gfortran compiler must be also installed to allow automatic compilation of the source code located in the ..//gsfit/unix directory, in order to generate a series of shared libraries, when gsfit is launched for the first time. WARNING: For this action to be successfully completed, the user must have writing rights to the ..//gsfit/unix directory.<br />
<br />
=GSFIT Windows OS Requirements=<br />
The GSFIT package is distributed along with a set of dynamic link libraries located in the ..//gsfit/win subfolder, which have been compiled assuming a WIN64 architecture. For Win32, please contact us to inquire about alternative options.<br />
<br />
=GSFIT SSW_UPGRADE Installation=<br />
The release version of the IDL GSFIT package is intended to be distributed through the SSW IDL repository [https://www.lmsal.com/solarsoft/]. <br />
Although installed as a stand-alone package, the GSFIT code relies on a series of IDL support routines that are part of the gx_simulator package. Therefore, in addition to installing the gsfit package , the gx_simulator package must be also installed. This installation can be performed by issuing an upgrade command, i.e.<br />
<br />
<pre><br />
IDL> ssw_upgrade,/gsfit,/gx_simulator,/gen,/spawn,/loud,/passive_ftp <br />
</pre><br />
<br />
=GSFIT Manual SWW Installation and Setup=<br />
However, if as of today the GSFIT package has not been yet released through SSW, you may perform a manual install by copying the directory structure located at https://github.com/Gelu-Nita/GSFIT to your local machine SSW directory, $ssw/packages/gsfit/' <br />
If such manual installation is performed, the $ssw/gen/setup/setup.ssw_env script must be edited by adding or altering the following lines:<br />
<pre><br />
setenv SSW_GSFIT $SSW_PACKAGES/gsfit$<br />
<br />
setenv SSW_PACKAGES_INSTR "packages/gsfit [...]"<br />
<br />
setenv SSW_PACKAGES_ALL "$SSW_GSFIT [...]"<br />
</pre><br />
<br />
where [...] denote the definitions already existent in the original setup.ssw_env script.<br />
<br />
=GSFIT SSW Instrument Setup=<br />
Please note that, regardless the method chosen to install any of these two packages, to ensure proper functionality, one should make sure that sswidl.bat (on Windows platforms) or cshrc (on Unix or Mac platforms) scripts are properly updated such as to include gx_simulator and gsfit in the SSW_INSTR path declaration, i.e.<br />
<pre><br />
set SSW_INSTR=gx_simulator, gsfit [...] <br />
</pre><br />
where [..] denotes any other SSW packages already installed.<br />
<br />
=GSFIT Manual Stand-Alone Installation=<br />
Although '''not reccomended''', one may in principle choose to install the gsfit and gx_simulator packages in standalone directories that are not part of the SSW repositories. However if this (not recommended) option is used, the gsfit and gx_simulator paths should be explicitly added to the IDL !path global variable, i.e. <br />
<br />
and explicitly add this path to your IDL path structure.<br />
<br />
<pre><br />
IDL> !path='..//gsfit/idl:'+!path<br />
IDL> !path='..//gx_simulator/idl:'+!path<br />
</pre><br />
<br />
where '''../''' should be replaced with the explicit paths to the respective local machine repositories.</div>Gnitahttp://ovsa.njit.edu//wiki/index.php?title=GSFIT_Installation&diff=3935GSFIT Installation2019-05-14T15:53:04Z<p>Gnita: </p>
<hr />
<div>[https://github.com/Gelu-Nita/GSFIT GSFIT] is an IDL-widget(GUI)-based spectral fitting package that provides a user-friendly display of [http://www.ovsa.njit.edu/ EOVSA] image cubes and an interface to fast fitting codes (via platform-dependent shared-object libraries). Fits to individual spectra can be done quickly for manual investigation using a GUI application called [http://www.ovsa.njit.edu/wiki/index.php/GSFIT_Help GSFIT], while parallel/multi-core batch processing of selected blocks of data can also be performed using a command prompt application called [http://www.ovsa.njit.edu/wiki/index.php/GSFITCP_Help GSFITCP]. A helper routine called [http://www.ovsa.njit.edu/wiki/index.php/GSFITVIEW_Help GSFITVIEW] allows further display and investigation of the fitting results. Please visit [GSFIT HELP], [GSFITCP HELP] and [GSFITVIEW HELP] pages for detailed information about these applications.<br />
<br />
=GSFIT Linux / Mac OS Requirements=<br />
On Mac and Unix platforms, the gfortran compiler must be also installed to allow automatic compilation of the source code located in the ..//gsfit/unix directory, in order to generate a series of shared libraries, when gsfit is launched for the first time. WARNING: For this action to be successfully completed, the user must have writing rights to the ..//gsfit/unix directory.<br />
<br />
=GSFIT Windows OS Requirements=<br />
The GSFIT package is distributed along with a set of dynamic link libraries located in the ..//gsfit/win subfolder, which have been compiled assuming a WIN64 architecture. For Win32, please contact us to inquire about alternative options.<br />
<br />
=GSFIT SSW_UPGRADE Installation=<br />
The release version of the IDL GSFIT package is intended to be distributed through the SSW IDL repository [https://www.lmsal.com/solarsoft/]. <br />
Although installed as a stand-alone package, the GSFIT code relies on a series of IDL support routines that are part of the gx_simulator package. Therefore, in addition to installing the gsfit package , the gx_simulator package must be also installed. This installation can be performed by issuing an upgrade command, i.e.<br />
<br />
<pre><br />
IDL> ssw_upgrade,/gsfit,/gx_simulator,/gen,/spawn,/loud,/passive_ftp <br />
</pre><br />
<br />
=GSFIT Manual SWW Installation and Setup=<br />
However, if as of today the GSFIT package has not been yet released through SSW, you may perform a manual install by copying the directory structure located at https://github.com/Gelu-Nita/GSFIT to your local machine SSW directory, $ssw/packages/gsfit/' <br />
If such manual installation is performed, the $ssw/gen/setup/setup.ssw_env script must be edited by adding or altering the following lines:<br />
<pre><br />
setenv SSW_GSFIT $SSW_PACKAGES/gsfit$<br />
<br />
setenv SSW_PACKAGES_INSTR "packages/gsfit [...]"<br />
<br />
setenv SSW_PACKAGES_ALL "$SSW_GSFIT [...]"<br />
</pre><br />
<br />
where [...] denote the definitions already existent in the original setup.ssw_env script.<br />
<br />
=GSFIT SSW Instrument Setup=<br />
Please note that, regardless the method chosen to install any of these two packages, to ensure proper functionality, one should make sure that sswidl.bat (on Windows platforms) or cshrc (on Unix or Mac platforms) scripts are properly updated such as to include gx_simulator and gsfit in the SSW_INSTR path declaration, i.e.<br />
<pre><br />
set SSW_INSTR=gx_simulator, gsfit [...] <br />
</pre><br />
where [..] denotes any other SSW packages already installed.<br />
<br />
=GSFIT Manual Stand-Alone Installation=<br />
Although '''not reccomended''', one may in principle choose to install the gsfit and gx_simulator packages in standalone directories that are not part of the SSW repositories. However if this (not recommended) option is used, the gsfit and gx_simulator paths should be explicitly added to the IDL !path global variable, i.e. <br />
<br />
and explicitly add this path to your IDL path structure.<br />
<br />
<pre><br />
IDL> !path='..//gsfit/idl:'+!path<br />
IDL> !path='..//gx_simulator/idl:'+!path<br />
</pre><br />
<br />
where '''../''' should be replaced with the explicit paths to the respective local machine repositories.</div>Gnitahttp://ovsa.njit.edu//wiki/index.php?title=GSFITCP_Help&diff=3934GSFITCP Help2019-05-14T15:46:30Z<p>Gnita: /* Launching the GSFITCP command prompt application */</p>
<hr />
<div>GSFITCP is the command prompt counterpart of the GSFIT GUI microwave spectral fitting application. Once started, GSFITCP is designed to run in unattended mode until all fitting tasks assigned to it are completed and log on the disk in an user-defined *.log file, the content of which may be visualized using the GSFITVIEW GUI application. When run remotely on an Linux/Mac platform, the GSFITCP may be launched on a detached [https://linuxize.com/post/how-to-use-linux-screen/ screen], which allows the remote user to logout without stopping the process in which GSFITCP runs.<br />
<br />
=GSFITCP Installation=<br />
GSFITCP is part of the GSFIT IDL Package<br />
<br />
To get installation instructions for the IDL GSFIT package, please visit the [[GSFIT Installation]] page.<br />
<br />
=Launching the GSFITCP command prompt application=<br />
<br />
To obtain a list of valid GSFIT calling sequences one may call '''''gsfitcp''''' with no arguments:<br />
<pre><br />
IDL> gsfitcp<br />
% GSFITCP: For a detailed description visit http://www.ovsa.njit.edu/wiki/index.php/GSFITCP_Help, or use one of the folowing calling sequences:<br />
% IDL-> gsfitcp, taskfilename; to provide a path to a stored GSFIT task stracture<br />
% IDL-> gsfitcp, taskstructure; to provide an already restored GSFIT task structure<br />
% IDL-> gsfitcp, nthreads; to set,increase, or decrease the number of ashyncronious threads to be used<br />
% IDL-> gsfitcp, out=out,log; to change the default "gsfitcp.log" path for run-time logging of the results.<br />
% IDL-> gsfitcp, /status; to report the status of the application<br />
% IDL-> gsfitcp, /quiet; to inhibit automatic printing of progress report messages at run-time<br />
% IDL-> gsfitcp, /start; to start processing the task queue<br />
% IDL-> gsfitcp, /flush; to flush the pending task queue<br />
% IDL-> gsfitcp, /abort; to abort all active tasks and flush the pending task queue<br />
% IDL-> gsfitcp, /exit; to abort all active tasks, flush the pending task queue, and exit the apllication<br />
% GSFITCP: % Any logical combination of the arguments and keywords listed above should result in a valid single-line calling sequence<br />
</pre></div>Gnitahttp://ovsa.njit.edu//wiki/index.php?title=GSFITCP_Help&diff=3933GSFITCP Help2019-05-14T15:45:51Z<p>Gnita: /* Launching the GSFITCP command prompt application */</p>
<hr />
<div>GSFITCP is the command prompt counterpart of the GSFIT GUI microwave spectral fitting application. Once started, GSFITCP is designed to run in unattended mode until all fitting tasks assigned to it are completed and log on the disk in an user-defined *.log file, the content of which may be visualized using the GSFITVIEW GUI application. When run remotely on an Linux/Mac platform, the GSFITCP may be launched on a detached [https://linuxize.com/post/how-to-use-linux-screen/ screen], which allows the remote user to logout without stopping the process in which GSFITCP runs.<br />
<br />
=GSFITCP Installation=<br />
GSFITCP is part of the GSFIT IDL Package<br />
<br />
To get installation instructions for the IDL GSFIT package, please visit the [[GSFIT Installation]] page.<br />
<br />
=Launching the GSFITCP command prompt application=<br />
<br />
To obtain a list of valid GSFIT calling sequences one may call '''''gsfitcp''''' with no arguments:<br />
<pre><br />
IDL> gsfitcp<br />
% GSFITCP: For a detailed description visit http://www.ovsa.njit.edu/wiki/index.php/GSFITCP_Help, or use one of the folowing calling sequences:<br />
% IDL-> gsfitcp, taskfilename; to provide a path to a stored GSFIT task stracture<br />
% IDL-> gsfitcp, taskstructure; to provide an already restored GSFIT task structure<br />
% IDL-> gsfitcp, nthreads; to set,increase, or decrease the number of ashyncronious threads to be used<br />
% IDL-> gsfitcp, out=out,log; to change the default "gsfitcp.log" path for run-time logging of the results.<br />
% IDL-> gsfitcp, /status; to report the status of the application<br />
% IDL-> gsfitcp, /quiet; to inhibit automatic printing of progress report messages at run-time<br />
% IDL-> gsfitcp, /start; to start processing the task queue<br />
% IDL-> gsfitcp, /flush; to flush the pending task queue<br />
% IDL-> gsfitcp, /abort; to abort all active tasks and flush the pending task queue<br />
% IDL-> gsfitcp, /exit; to abort all active tasks, flush the pending task queue, and exit the apllication<br />
% GSFITCP: % Any logical combination of the arguments and keywords listed above should result in a valid calling sequence<br />
</pre></div>Gnitahttp://ovsa.njit.edu//wiki/index.php?title=GSFITCP_Help&diff=3932GSFITCP Help2019-05-14T15:45:38Z<p>Gnita: /* Launching the GSFITCP command prompt application */</p>
<hr />
<div>GSFITCP is the command prompt counterpart of the GSFIT GUI microwave spectral fitting application. Once started, GSFITCP is designed to run in unattended mode until all fitting tasks assigned to it are completed and log on the disk in an user-defined *.log file, the content of which may be visualized using the GSFITVIEW GUI application. When run remotely on an Linux/Mac platform, the GSFITCP may be launched on a detached [https://linuxize.com/post/how-to-use-linux-screen/ screen], which allows the remote user to logout without stopping the process in which GSFITCP runs.<br />
<br />
=GSFITCP Installation=<br />
GSFITCP is part of the GSFIT IDL Package<br />
<br />
To get installation instructions for the IDL GSFIT package, please visit the [[GSFIT Installation]] page.<br />
<br />
=Launching the GSFITCP command prompt application=<br />
<br />
To obtain a list of valid GSFIT calling sequences one may call'''''gsfitcp''''' with no arguments:<br />
<pre><br />
IDL> gsfitcp<br />
% GSFITCP: For a detailed description visit http://www.ovsa.njit.edu/wiki/index.php/GSFITCP_Help, or use one of the folowing calling sequences:<br />
% IDL-> gsfitcp, taskfilename; to provide a path to a stored GSFIT task stracture<br />
% IDL-> gsfitcp, taskstructure; to provide an already restored GSFIT task structure<br />
% IDL-> gsfitcp, nthreads; to set,increase, or decrease the number of ashyncronious threads to be used<br />
% IDL-> gsfitcp, out=out,log; to change the default "gsfitcp.log" path for run-time logging of the results.<br />
% IDL-> gsfitcp, /status; to report the status of the application<br />
% IDL-> gsfitcp, /quiet; to inhibit automatic printing of progress report messages at run-time<br />
% IDL-> gsfitcp, /start; to start processing the task queue<br />
% IDL-> gsfitcp, /flush; to flush the pending task queue<br />
% IDL-> gsfitcp, /abort; to abort all active tasks and flush the pending task queue<br />
% IDL-> gsfitcp, /exit; to abort all active tasks, flush the pending task queue, and exit the apllication<br />
% GSFITCP: % Any logical combination of the arguments and keywords listed above should result in a valid calling sequence<br />
</pre></div>Gnitahttp://ovsa.njit.edu//wiki/index.php?title=GSFITCP_Help&diff=3931GSFITCP Help2019-05-14T15:41:15Z<p>Gnita: /* Launching the GSFITCP command prompt application */</p>
<hr />
<div>GSFITCP is the command prompt counterpart of the GSFIT GUI microwave spectral fitting application. Once started, GSFITCP is designed to run in unattended mode until all fitting tasks assigned to it are completed and log on the disk in an user-defined *.log file, the content of which may be visualized using the GSFITVIEW GUI application. When run remotely on an Linux/Mac platform, the GSFITCP may be launched on a detached [https://linuxize.com/post/how-to-use-linux-screen/ screen], which allows the remote user to logout without stopping the process in which GSFITCP runs.<br />
<br />
=GSFITCP Installation=<br />
GSFITCP is part of the GSFIT IDL Package<br />
<br />
To get installation instructions for the IDL GSFIT package, please visit the [[GSFIT Installation]] page.<br />
<br />
=Launching the GSFITCP command prompt application=<br />
<br />
To obtain a list of valid GSFIT calling sequences one may call'''''gsfitcp''''' with no arguments:<br />
<pre><br />
IDL> gsfitcp<br />
% GSFITCP: For a detailed description visit http://www.ovsa.njit.edu/wiki/index.php/GSFITCP_Help, or use one of the folowing calling sequences:<br />
% IDL-> gsfitcp, taskfilename; to provide a path to a stored GSFIT task stracture<br />
% IDL-> gsfitcp, taskstructure; to provide an already restored GSFIT task structure<br />
% IDL-> gsfitcp, nthreads; to set,increase, or decrease the number of ashyncronious threads to be used<br />
% IDL-> gsfitcp, out=out,log; to change the default "gsfitcp.log" path for run-time logging of the results.<br />
% IDL-> gsfitcp, /status; to report the status of the application<br />
% IDL-> gsfitcp, /quiet; to inhibit automatic printing of progress report messages at run-time<br />
% IDL-> gsfitcp, /start; to start processing the task queue<br />
% IDL-> gsfitcp, /flush; to flush the pending task queue<br />
% IDL-> gsfitcp, /abort; to abort all active tasks and flush the pending task queue<br />
% IDL-> gsfitcp, /exit; to abort all active tasks, flush the pending task queue, and exit the apllication<br />
% IDL-> gsfitcp,taskfilename,/start; This minimal call sequence should get you started on one thread!<br />
</pre></div>Gnitahttp://ovsa.njit.edu//wiki/index.php?title=GSFITCP_Help&diff=3930GSFITCP Help2019-05-14T15:41:04Z<p>Gnita: /* Launching the GSFITCP command prompt application */</p>
<hr />
<div>GSFITCP is the command prompt counterpart of the GSFIT GUI microwave spectral fitting application. Once started, GSFITCP is designed to run in unattended mode until all fitting tasks assigned to it are completed and log on the disk in an user-defined *.log file, the content of which may be visualized using the GSFITVIEW GUI application. When run remotely on an Linux/Mac platform, the GSFITCP may be launched on a detached [https://linuxize.com/post/how-to-use-linux-screen/ screen], which allows the remote user to logout without stopping the process in which GSFITCP runs.<br />
<br />
=GSFITCP Installation=<br />
GSFITCP is part of the GSFIT IDL Package<br />
<br />
To get installation instructions for the IDL GSFIT package, please visit the [[GSFIT Installation]] page.<br />
<br />
=Launching the GSFITCP command prompt application=<br />
<br />
To obtain a list of valid GSFIT calling sequences one may call'''''gsfitcp''''' with no arguments:<br />
</pre><br />
IDL> gsfitcp<br />
% GSFITCP: For a detailed description visit http://www.ovsa.njit.edu/wiki/index.php/GSFITCP_Help, or use one of the folowing calling sequences:<br />
% IDL-> gsfitcp, taskfilename; to provide a path to a stored GSFIT task stracture<br />
% IDL-> gsfitcp, taskstructure; to provide an already restored GSFIT task structure<br />
% IDL-> gsfitcp, nthreads; to set,increase, or decrease the number of ashyncronious threads to be used<br />
% IDL-> gsfitcp, out=out,log; to change the default "gsfitcp.log" path for run-time logging of the results.<br />
% IDL-> gsfitcp, /status; to report the status of the application<br />
% IDL-> gsfitcp, /quiet; to inhibit automatic printing of progress report messages at run-time<br />
% IDL-> gsfitcp, /start; to start processing the task queue<br />
% IDL-> gsfitcp, /flush; to flush the pending task queue<br />
% IDL-> gsfitcp, /abort; to abort all active tasks and flush the pending task queue<br />
% IDL-> gsfitcp, /exit; to abort all active tasks, flush the pending task queue, and exit the apllication<br />
% IDL-> gsfitcp,taskfilename,/start; This minimal call sequence should get you started on one thread!<br />
</pre></div>Gnitahttp://ovsa.njit.edu//wiki/index.php?title=GSFITCP_Help&diff=3929GSFITCP Help2019-05-14T01:13:52Z<p>Gnita: /* Launching the GSFITCP command prompt application */</p>
<hr />
<div>GSFITCP is the command prompt counterpart of the GSFIT GUI microwave spectral fitting application. Once started, GSFITCP is designed to run in unattended mode until all fitting tasks assigned to it are completed and log on the disk in an user-defined *.log file, the content of which may be visualized using the GSFITVIEW GUI application. When run remotely on an Linux/Mac platform, the GSFITCP may be launched on a detached [https://linuxize.com/post/how-to-use-linux-screen/ screen], which allows the remote user to logout without stopping the process in which GSFITCP runs.<br />
<br />
=GSFITCP Installation=<br />
GSFITCP is part of the GSFIT IDL Package<br />
<br />
To get installation instructions for the IDL GSFIT package, please visit the [[GSFIT Installation]] page.<br />
<br />
=Launching the GSFITCP command prompt application=<br />
<br />
GSFITCP is launched using the following call:<br />
<pre><br />
IDL> gsfitcp, taskfile[, nthreads, start=start, quiet=quiet] <br />
</pre><br />
where <br />
*'''''taskfile''''' is a mandatory string argument indication the path to a file in which a GSFIT task has been previously saved, as explained in the [[GSFIT Help]] page. Alternatively, the string argument '''''taskfile''''' may be replaced by an IDL task structure that has ben previously restored from such a task file.<br />
*'''''nthreads''''' is an optional argument indicating the number of parallel asynchronous threads to be used <br />
*'''''/start''''' is an optinal keyword that, if set, requests immediate start of the batch processing<br />
*'''''/quiet''''' is an optional keyword that, if set, prevents GSFITCP to print periodic run-time messages reporting the progress of the fitting process. <br />
<br />
A detailed description of the GSFITCP functionality is provided below.</div>Gnitahttp://ovsa.njit.edu//wiki/index.php?title=GSFITCP_Help&diff=3928GSFITCP Help2019-05-14T01:12:14Z<p>Gnita: /* Launching the GSFITCP command prompt application */</p>
<hr />
<div>GSFITCP is the command prompt counterpart of the GSFIT GUI microwave spectral fitting application. Once started, GSFITCP is designed to run in unattended mode until all fitting tasks assigned to it are completed and log on the disk in an user-defined *.log file, the content of which may be visualized using the GSFITVIEW GUI application. When run remotely on an Linux/Mac platform, the GSFITCP may be launched on a detached [https://linuxize.com/post/how-to-use-linux-screen/ screen], which allows the remote user to logout without stopping the process in which GSFITCP runs.<br />
<br />
=GSFITCP Installation=<br />
GSFITCP is part of the GSFIT IDL Package<br />
<br />
To get installation instructions for the IDL GSFIT package, please visit the [[GSFIT Installation]] page.<br />
<br />
=Launching the GSFITCP command prompt application=<br />
<br />
GSFITCP is launched using the following call:<br />
<pre><br />
IDL> gsfitcp, taskfile[, nthreads, start=start, quiet=quiet] <br />
</pre><br />
where <br />
*'''''taskfile''''' is a mandatory string argument indication the path to a file in which a GSFIT task has been previously saved, as explained in the [[GSFIT Help]] page<br />
*'''''nthreads''''' is an optional argument indicating the number of parallel asynchronous threads to be used <br />
*'''''/start''''' is an optinal keyword that, if set, requests immediate start of the batch processing<br />
*'''''/quiet''''' is an optional keyword that, if set, prevents GSFITCP to print periodic run-time messages reporting the progress of the fitting process. <br />
<br />
A detailed description of the GSFITCP functionality is provided below.</div>Gnitahttp://ovsa.njit.edu//wiki/index.php?title=GSFITCP_Help&diff=3927GSFITCP Help2019-05-14T01:11:53Z<p>Gnita: /* Launching the GSFITCP command prompt application */</p>
<hr />
<div>GSFITCP is the command prompt counterpart of the GSFIT GUI microwave spectral fitting application. Once started, GSFITCP is designed to run in unattended mode until all fitting tasks assigned to it are completed and log on the disk in an user-defined *.log file, the content of which may be visualized using the GSFITVIEW GUI application. When run remotely on an Linux/Mac platform, the GSFITCP may be launched on a detached [https://linuxize.com/post/how-to-use-linux-screen/ screen], which allows the remote user to logout without stopping the process in which GSFITCP runs.<br />
<br />
=GSFITCP Installation=<br />
GSFITCP is part of the GSFIT IDL Package<br />
<br />
To get installation instructions for the IDL GSFIT package, please visit the [[GSFIT Installation]] page.<br />
<br />
=Launching the GSFITCP command prompt application=<br />
<br />
GSFITCP is launched using the following call:<br />
<pre><br />
IDL> gsfitcp, taskfile[, nthreads, start=start, quiet=quiet] <br />
</pre><br />
where <br />
*'''''taskfile''''' is a mandatory string argument indication the path to a file in which a GSFIT task has been previously saved, as explained in the [[GSFIT Help]] page<br />
*'''''nthreads''''' is an optional argument indicating the number of parallel asynchronous threads to be used <br />
*'''''/start''''' is an optinal keyword that, if set, requests immediate start of the batch processing<br />
*'''''/quiet''''' is an optional keyword that, if set, prevents GSFITCP to print periodic run-time messages reporting the progress of the fitting process. <br />
<br />
Since the fitting tasks are processed by GSFITCP <br />
<br />
A detailed description of the GSFITCP functionality is provided below.</div>Gnitahttp://ovsa.njit.edu//wiki/index.php?title=GSFITCP_Help&diff=3926GSFITCP Help2019-05-14T01:11:40Z<p>Gnita: /* Launching the GSFITCP command prompt application */</p>
<hr />
<div>GSFITCP is the command prompt counterpart of the GSFIT GUI microwave spectral fitting application. Once started, GSFITCP is designed to run in unattended mode until all fitting tasks assigned to it are completed and log on the disk in an user-defined *.log file, the content of which may be visualized using the GSFITVIEW GUI application. When run remotely on an Linux/Mac platform, the GSFITCP may be launched on a detached [https://linuxize.com/post/how-to-use-linux-screen/ screen], which allows the remote user to logout without stopping the process in which GSFITCP runs.<br />
<br />
=GSFITCP Installation=<br />
GSFITCP is part of the GSFIT IDL Package<br />
<br />
To get installation instructions for the IDL GSFIT package, please visit the [[GSFIT Installation]] page.<br />
<br />
=Launching the GSFITCP command prompt application=<br />
<br />
GSFITCP is launched using the following call:<br />
<pre><br />
IDL> gsfitcp, taskfile[, nthreads, start=start, quiet=quiet] <br />
</pre><br />
where <br />
*'''''taskfile''''' is a mandatory string argument indication the path to a file in which a GSFIT task has been previously saved, as explained in the [[GSFIT Help]] page<br />
*'''''nthreads''''' is an optional argument indicating the number of parallel asynchronous threads to be used <br />
*'''''/start''''', is an optinal keyword that, if set, requests immediate start of the batch processing<br />
*'''''/quiet''''' is an optional keyword that, if set, prevents GSFITCP to print periodic run-time messages reporting the progress of the fitting process. <br />
<br />
Since the fitting tasks are processed by GSFITCP <br />
<br />
A detailed description of the GSFITCP functionality is provided below.</div>Gnitahttp://ovsa.njit.edu//wiki/index.php?title=GSFITCP_Help&diff=3925GSFITCP Help2019-05-14T01:11:25Z<p>Gnita: /* Launching the GSFITCP command prompt application */</p>
<hr />
<div>GSFITCP is the command prompt counterpart of the GSFIT GUI microwave spectral fitting application. Once started, GSFITCP is designed to run in unattended mode until all fitting tasks assigned to it are completed and log on the disk in an user-defined *.log file, the content of which may be visualized using the GSFITVIEW GUI application. When run remotely on an Linux/Mac platform, the GSFITCP may be launched on a detached [https://linuxize.com/post/how-to-use-linux-screen/ screen], which allows the remote user to logout without stopping the process in which GSFITCP runs.<br />
<br />
=GSFITCP Installation=<br />
GSFITCP is part of the GSFIT IDL Package<br />
<br />
To get installation instructions for the IDL GSFIT package, please visit the [[GSFIT Installation]] page.<br />
<br />
=Launching the GSFITCP command prompt application=<br />
<br />
GSFITCP is launched using the following call:<br />
<pre><br />
IDL> gsfitcp, taskfile[, nthreads, start=start, quiet=quiet] <br />
</pre><br />
where <br />
*'''''taskfile''''' is a mandatory string argument indication the path to a file in which a GSFIT task has been previously saved, as explained in the [[GSFIT Help]] page<br />
*'''''nthreads''''' is an optional argument indicating the number of parallel asynchronous threads to be used <br />
*'''''/start''''', is an optinal keyword that, if set, requests immediate start of the batch processing<br />
*''''/quiet''''' is an optional keyword that, if set, prevents GSFITCP to print periodic run-time messages reporting the progress of the fitting process. <br />
<br />
Since the fitting tasks are processed by GSFITCP <br />
<br />
A detailed description of the GSFITCP functionality is provided below.</div>Gnitahttp://ovsa.njit.edu//wiki/index.php?title=GSFITCP_Help&diff=3924GSFITCP Help2019-05-14T01:11:02Z<p>Gnita: /* Launching the GSFITCP command prompt application */</p>
<hr />
<div>GSFITCP is the command prompt counterpart of the GSFIT GUI microwave spectral fitting application. Once started, GSFITCP is designed to run in unattended mode until all fitting tasks assigned to it are completed and log on the disk in an user-defined *.log file, the content of which may be visualized using the GSFITVIEW GUI application. When run remotely on an Linux/Mac platform, the GSFITCP may be launched on a detached [https://linuxize.com/post/how-to-use-linux-screen/ screen], which allows the remote user to logout without stopping the process in which GSFITCP runs.<br />
<br />
=GSFITCP Installation=<br />
GSFITCP is part of the GSFIT IDL Package<br />
<br />
To get installation instructions for the IDL GSFIT package, please visit the [[GSFIT Installation]] page.<br />
<br />
=Launching the GSFITCP command prompt application=<br />
<br />
GSFITCP is launched using the following call:<br />
<pre><br />
IDL> gsfitcp, taskfile[, nthreads, start=start, quiet=quiet] <br />
</pre><br />
where <br />
*'''''taskfile''''' is a mandatory string argument indication the path to a file in which a GSFIT task has been previously saved, as explained in the [[GSFIT Help]] page<br />
*'''''nthreads''''' is an optional argument indicating the number of parallel asynchronous threads to be used <br />
*'''''/start''''', is an optinal keyword that, if set, requests immediate start of the batch processing<br />
*'''''/start''''' is an optional keyword that, if set, prevents GSFITCP to print periodic run-time messages reporting the progress of the fitting process. <br />
<br />
Since the fitting tasks are processed by GSFITCP <br />
<br />
A detailed description of the GSFITCP functionality is provided below.</div>Gnitahttp://ovsa.njit.edu//wiki/index.php?title=GSFITCP_Help&diff=3923GSFITCP Help2019-05-14T01:10:50Z<p>Gnita: /* Launching the GSFITCP command prompt application */</p>
<hr />
<div>GSFITCP is the command prompt counterpart of the GSFIT GUI microwave spectral fitting application. Once started, GSFITCP is designed to run in unattended mode until all fitting tasks assigned to it are completed and log on the disk in an user-defined *.log file, the content of which may be visualized using the GSFITVIEW GUI application. When run remotely on an Linux/Mac platform, the GSFITCP may be launched on a detached [https://linuxize.com/post/how-to-use-linux-screen/ screen], which allows the remote user to logout without stopping the process in which GSFITCP runs.<br />
<br />
=GSFITCP Installation=<br />
GSFITCP is part of the GSFIT IDL Package<br />
<br />
To get installation instructions for the IDL GSFIT package, please visit the [[GSFIT Installation]] page.<br />
<br />
=Launching the GSFITCP command prompt application=<br />
<br />
GSFITCP is launched using the following call:<br />
<pre><br />
IDL> gsfitcp, taskfile[, nthreads, start=start, quiet=quiet] <br />
</pre><br />
where <br />
*'''''taskfile''''' is a mandatory string argument indication the path to a file in which a GSFIT task has been previously saved, as explained in the [[GSFIT Help]] page<br />
*'''''nthreads''''' is an optional argument indicating the number of parallel asynchronous threads to be used <br />
'''''/start''''', is an optinal keyword that, if set, requests immediate start of the batch processing<br />
*'''''/start''''' is an optional keyword that, if set, prevents GSFITCP to print periodic run-time messages reporting the progress of the fitting process. <br />
<br />
Since the fitting tasks are processed by GSFITCP <br />
<br />
A detailed description of the GSFITCP functionality is provided below.</div>Gnitahttp://ovsa.njit.edu//wiki/index.php?title=GSFITCP_Help&diff=3922GSFITCP Help2019-05-14T01:08:44Z<p>Gnita: /* Launching the GSFITCP command prompt application */</p>
<hr />
<div>GSFITCP is the command prompt counterpart of the GSFIT GUI microwave spectral fitting application. Once started, GSFITCP is designed to run in unattended mode until all fitting tasks assigned to it are completed and log on the disk in an user-defined *.log file, the content of which may be visualized using the GSFITVIEW GUI application. When run remotely on an Linux/Mac platform, the GSFITCP may be launched on a detached [https://linuxize.com/post/how-to-use-linux-screen/ screen], which allows the remote user to logout without stopping the process in which GSFITCP runs.<br />
<br />
=GSFITCP Installation=<br />
GSFITCP is part of the GSFIT IDL Package<br />
<br />
To get installation instructions for the IDL GSFIT package, please visit the [[GSFIT Installation]] page.<br />
<br />
=Launching the GSFITCP command prompt application=<br />
<br />
GSFITCP is launched using the following call:<br />
<pre><br />
IDL> gsfitcp, taskfile[, nthreads, start=start, quiet=quiet] <br />
</pre><br />
where '''''taskfile''''' is a mandatory string argument indication the path to a file in which a GSFIT task has been previously saved, as explained in the [[GSFIT Help]] page, '''''nthreads''''' is an optional argument indicating the number of parallel asynchronous threads to be used, the optional keyword '''''/start''''', if set, requests immediate start of the batch processing, and the optional keyword'''''/start''''', if set, prevents GSFITCP to print periodic run-time messages reporting the progress of the fitting process. <br />
<br />
Since the fitting tasks are processed by GSFITCP <br />
<br />
A detailed description of the GSFITCP functionality is provided below.</div>Gnitahttp://ovsa.njit.edu//wiki/index.php?title=GSFITCP_Help&diff=3921GSFITCP Help2019-05-14T01:07:51Z<p>Gnita: /* Launching the GSFITCP command prompt application */</p>
<hr />
<div>GSFITCP is the command prompt counterpart of the GSFIT GUI microwave spectral fitting application. Once started, GSFITCP is designed to run in unattended mode until all fitting tasks assigned to it are completed and log on the disk in an user-defined *.log file, the content of which may be visualized using the GSFITVIEW GUI application. When run remotely on an Linux/Mac platform, the GSFITCP may be launched on a detached [https://linuxize.com/post/how-to-use-linux-screen/ screen], which allows the remote user to logout without stopping the process in which GSFITCP runs.<br />
<br />
=GSFITCP Installation=<br />
GSFITCP is part of the GSFIT IDL Package<br />
<br />
To get installation instructions for the IDL GSFIT package, please visit the [[GSFIT Installation]] page.<br />
<br />
=Launching the GSFITCP command prompt application=<br />
<br />
GSFITCP is launched using the following call:<br />
<pre><br />
IDL> gsfitcp, taskfile[, nthreads, start=start, quiet=quiet] <br />
</pre><br />
where '''''taskfile''''' is a path to a file in which a GSFIT task has been previously saved, as explained in the [[GSFIT Help]] page, '''''nthreads''''' is an optional argument indicating the number of parallel asynchronous threads to be used, the optional keyword '''''/start''''', if set, requests immediate start of the batch processing, and the optional keyword'''''/start''''', if set, prevents GSFITCP to print periodic run-time messages reporting the progress of the fitting process. <br />
<br />
Since the fitting tasks are processed by GSFITCP <br />
<br />
A detailed description of the GSFITCP functionality is provided below.</div>Gnitahttp://ovsa.njit.edu//wiki/index.php?title=GSFITCP_Help&diff=3920GSFITCP Help2019-05-14T01:07:25Z<p>Gnita: /* GSFITCP Installation */</p>
<hr />
<div>GSFITCP is the command prompt counterpart of the GSFIT GUI microwave spectral fitting application. Once started, GSFITCP is designed to run in unattended mode until all fitting tasks assigned to it are completed and log on the disk in an user-defined *.log file, the content of which may be visualized using the GSFITVIEW GUI application. When run remotely on an Linux/Mac platform, the GSFITCP may be launched on a detached [https://linuxize.com/post/how-to-use-linux-screen/ screen], which allows the remote user to logout without stopping the process in which GSFITCP runs.<br />
<br />
=GSFITCP Installation=<br />
GSFITCP is part of the GSFIT IDL Package<br />
<br />
To get installation instructions for the IDL GSFIT package, please visit the [[GSFIT Installation]] page.<br />
<br />
=Launching the GSFITCP command prompt application=<br />
<br />
GSFITCP is launched using the following call:<br />
<pre><br />
IDL> gsfitcp, taskfile [, nthreads, start=start, quiet=quiet] <br />
</pre><br />
where '''''taskfile''''' is a path to a file in which a GSFIT task has been previously saved, as explained in the [[GSFIT Help]] page, '''''nthreads''''' is an optional argument indicating the number of parallel asynchronous threads to be used, the optional keyword '''''/start''''', if set, requests immediate start of the batch processing, and the optional keyword'''''/start''''', if set, prevents GSFITCP to print periodic run-time messages reporting the progress of the fitting process. <br />
<br />
Since the fitting tasks are processed by GSFITCP <br />
<br />
A detailed description of the GSFITCP functionality is provided below.</div>Gnitahttp://ovsa.njit.edu//wiki/index.php?title=GSFITCP_Help&diff=3919GSFITCP Help2019-05-14T00:53:02Z<p>Gnita: </p>
<hr />
<div>GSFITCP is the command prompt counterpart of the GSFIT GUI microwave spectral fitting application. Once started, GSFITCP is designed to run in unattended mode until all fitting tasks assigned to it are completed and log on the disk in an user-defined *.log file, the content of which may be visualized using the GSFITVIEW GUI application. When run remotely on an Linux/Mac platform, the GSFITCP may be launched on a detached [https://linuxize.com/post/how-to-use-linux-screen/ screen], which allows the remote user to logout without stopping the process in which GSFITCP runs.<br />
<br />
=GSFITCP Installation=<br />
GSFITCP is part of the GSFIT IDL Package<br />
<br />
To get installation instructions for the IDL GSFIT package, please visit the [[GSFIT Installation]] page.<br />
<br />
GSFITCP is launched using the following call:<br />
<pre><br />
IDL> gsfitcp, taskfile, nthreads, /start<br />
</pre><br />
where '''''taskfile''''' is a path to a file in which a GSFIT task has been previously saved, as explained in the [[GSFIT Help]] page, '''''nthreads''''' is an optional argument indicating the number of parallel asynchronous threads to be used, and the optional keyword '''''/start''''', if set, requests immediate start of the batch processing. <br />
<br />
A detailed description of the GSFITCP functionality is provided in the page linked below.</div>Gnita