Difference between revisions of "GSFIT Installation"
|Line 1:||Line 1:|
We have developed a IDL-widget(GUI)-based spectral fitting package called [http://www.ovsa.njit.edu/wiki/index.php/GSFIT_Help
We have developed a IDL-widget(GUI)-based spectral fitting package called [http://www.ovsa.njit.edu/wiki/index.php/GSFIT_Help ], which provides a user-friendly display of 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, 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 ]. A helper routine called [http://www.ovsa.njit.edu/wiki/index.php/GSFITVIEW_Help ] allows further display and investigation of the fitting results.
===GSFIT Linux / Mac OS Requirements===
===GSFIT Linux / Mac OS Requirements===
Revision as of 16:16, 11 May 2019
We have developed 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). Fits to individual spectra can be done quickly for manual investigation, while parallel/multi-core batch processing of selected blocks of data can also be performed using a command prompt application called GSFITCP. A helper routine called GSFITVIEW allows further display and investigation of the fitting results.
GSFIT Linux / Mac OS Requirements
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.
GSFIT Windows OS Requirements
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.
GSFIT SSW_UPGRADE Instalation
The release version of the IDL GSFIT package is intended to be distributed through the SSW IDL repository . 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.
GSFIT Manual SWW Installation and Setup
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/' If such manual installation is performed, the $ssw/gen/setup/setup.ssw_env script must be edited by adding or altering the following lines:
setenv SSW_GSFIT $SSW_PACKAGES/gsfit$ setenv SSW_PACKAGES_INSTR "packages/gsfit [...]" setenv SSW_PACKAGES_ALL "$SSW_GSFIT [...]"
where [...] denote the definitions already existent in the original setup.ssw_env script.
GSFIT SSW Instrument Setup
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.
set SSW_INSTR=gx_simulator, gsfit [...]
where [..] denotes any other SSW packages already installed.
GSFIT Manual Stand-Alone Installation
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.
and explicitly add this path to your IDL path structure.
IDL> !path='..//gsfit/idl:'+!path IDL> !path='..//gx_simulator/idl:'+!path
where ../ should be replaced with the explicit paths to the respective local machine repositories.