The CIMA User's Log

Modifications to CIMA

Note that modifications reported in the CIMA engineering log or the CIMAFITS log are NOT repeated on this page.
You can return to the main CIMA page by clicking here.

The CIMA version history log is the most up-to-date page which lists all changes made to different versions of CIMA.

08 May 2014: Stop and Abort added in command file observing

'ABORT' and 'STOP' commands have been added for command file observing. So if you want to stop at the middle of your command file, you can use either of these commands. They are exactly same in functionality as the 'ABORT' and 'STOP' button. This change was made to the Stable and PUPPI version of CIMA.

20 Mar 2014: Modified warning for ALFA Bias Monitoring

Previously information from ALFA log file was used to warn users when alfa bias monitering was on. This sometimes gave false result as the log file were not always in sync with operators console. Now cima uses the same source of information as the operators console, to check if alfa monitoring is on/off. Also the pop up window has been replaced with non-interfering warning log message.

23 Sep 2013: Fixed Mock time domain sampling bug

Fixed a typo bug which affected 4 bit time domian sampling for 1 polarization.

13 Aug 2013: Addition of Noiseshift in Mock spectrometer

The 'pshift' in Mock Sectrometer backend menu sets how often downshifts are done in the fft butterflys. 'Radarshift' will down shift on the 1st 9 butterflys and then alternate every other butterfly. 'Noiseshift' will down shift every other butterfly.
Use 'radarshift' for L-band (with its large radars). It protects from overflows in the butterflys. The downside is that it may cause steps (in the freq direction) spaced by powers of 2. Use 'noiseshift' for receivers lacking radars (everything but L-band). Prior to 15oct12 pshift was set to 'radarshift'. The current default is still 'radarshift', to be compatible with pre 15oct12 observations.

01 Aug 2013: Fixed Azimuth Scan

The LST are adjusted for cases of midnight rollover, so that they are within 24 hour range. This has only been applied to Fixed Azimuth drift scan mode.

22 Apr 2013: ProjectID Area

In 'Line' mode, CIMA will look for project directory first in '/share/obs4/usr/', and if not found, then in '/share/obs4/usr/pulsars' . In 'Pulsar' mode, CIMA will first look for project directory in '/share/obs4/usr/pulsar', and if not found, then in '/share/obs4/usr/'.

Current setup wont be affected. Problems might happen if there is project directory both in '/share/obs4/usr/' and '/share/obs4/usr/pulsar'.
So I would seek your help to :

11 Apr 2013: Warning for ALFA Bias Monitoring

22 Feb 2013: Read line last of CMD file even without end-of-line marker

13 Nov 2012: SBN has now hcorcal

05 Apr 2012: Max Waittime for Fixed Azimuth Observation

05 Apr 2012: Parsing Polyco files using WAPP

02 Apr 2012: interim correlator using 1 GHz IF

15 Mar 2012: Mock spectrometer bandwidth display

31 Oct 2011: command file timeout loading mock config files

When both groups of mock spectrometers are used there can be a total of 14 spectrometer boxes to configure. When command file observing configures a backend, it times out after 10 seconds. With all 14 mocks it occasionally took longer than 10 seconds. The fix was to increase the timeout to 20 seconds. The error reported by the command file code now includes the reason for the timeout.
Files:Executive/command_files.tcl (load_config_file()) SVN revision;1463 (this was committed months later)

16 June 2011: Mock spectrometer time domain sampling

14 Nov 2010: fix show_iflo() bug

Version a.1.02 fixed a bug in iflo_display.tcl function: show_iflo(). Had j>=4. needed $j >=4.

18 Oct 2010: mocksp config files work with mock_adjpwr keyword of svnwork

This svnwork version added the mock_adjpwr key to the mock setup. This keyword was not present in mocksp ver 3.2.05. If a mocksp config file was used with the svnwork version, it would fail saying that setup(mock_adjpwr) did not exist. This has been fixed so the mocksp config file can be used with svnwork. In this case mock_adjpwr is set to the default value of 30 counts

17 Oct 2010: svnwork mods thru 17oct10

22 Mar 2010: mock single pixel configuration bug

The configuration menu for single pixel mock observing would occasionally give an error "set mock(xxxxx) expected integer but got floating point number. The problem was the tcl incr command was being used on a float variable. The fix was to set the variable with int() rather than floor(). The bug was in Frontend/backend_mock.tcl:check_mock_configuration(). Version changes: mocksp:(3.2.04 to 3.2.05). Other versions not affected. svn revision 1304

02 Feb 2010: increase max integration time for Mocks

Cima was limiting the maximum integration time for the wapps and mock spectrometers to 1200 seconds. The max integration time for the mock spectrometers was increased to 9999 secs. The change was in Frontend/observer.tcl:check_obsmode_options(). Version changes: mocksp:(3.2.03 to 3.2.04). Other versions not affected. svn revsion 1303

13 Jan 2010: CIMA interim correlator 2010 scan problems

Cima was not displaying the scan number in the status window for the interim correlator observations. The scan number format is Ydddnnnnn where Y is the last digit of the year. For 2010 this is a 0. Cima always assumed there were 9 digits in the scan number. The interim correlator messages were not sending the leadings 0's. This messed up Cima's parsing of the messages. message.tcl was updated to fix the parsing. The actual data in the corfiles had the correct scan number. Version changes: mocksp:(3.2.03 to 3.2.04) smart:(3.7.07 to 3.1.08) normal:(3.0.13 to 3.0.14) old:(not updated). svn revision 1261.

12 Jan 2010: wapp/mock scan number problem for year 2010

The scan number format is Ydddnnnn where Y is the last digit of the year. For 2010 this is a 0. When incrementing the scan number, cima was adding 1 to 0dddnnnn. In Tcl numbers with leading zeros are octal. Tcl would convert the "octal" number to decimal and then do the add. This caused scan numbers whose decimal format did not match the Ydddnnnnn format. The fix stripped off the leading 0's. This bug applied to the wapp and mock data (the cima use of the interim correlator has other problems to be fixed..) Version changes: old:(2.2.39 to 2.2.40), normal:(3.0.12 to 3.0.13), smart:(3.1.06 to 3.1.07), mocksp:(3.2.01 to 3.2.02). svn revision 1261.

22 Nov 2009: basketweave rate error in azza mode.

The azza mode of basketweave would use a za rate of 0 if declen was less than secs. It was doing an integer divide : rate= declen/secs. Updated to be float: rate = (1.*declen)/secs. This error did not occur in smartbasket. Version changes: old:(2.2.38 to 2.2.39), normal:(3.0.11 to 3.0.12), smart:(3.1.05 to 3.1.06), mocksp:(3.2.00 to 3.2.01). svn revision 1228.

18 May 2009: wapp radar blanker fix (Version 3.X)

In versions 3.[0-1] (smart and normal) the radar blanker was not working with the wapps. The symptom was that cima would appear to enable the blanker, but no FAA blanking was actually done. The problem was the conversion of the blanking code from (0,1) to "off,on". When the data was loaded into the fits header, "off/on" was being passed rather than 0,1 (the correct header values). This has now been fixed in the Smart (3.1.05) and Normal (3.0.11). svn revision r1147

21 April 2009: ASP/30-MHz and ISUP/ISOK bug fixes (Version 3.1)

This fix addresses two bugs in CIMA. The first only affects pulsar observers using ASP and/or the 30-MHz in parallel with the WAPPs. If an observer use any of these together with a WAPP bandwidth of less than 100 MHz and enable the 'All equal' button for the WAPPs to keep all the WAPP boards equal, then the bandwidth will jump back automatically to 100 MHz when the 'Accept' or 'Apply' button is pressed. This has now been fixed in CIMA version 3.1 (called 'Smart') - however, the problem also exists in version 3.0 (called 'Normal') where it has not been fixed.

The second problem only affects CIMA version 3.1 where the new conditional function 'ISOK' was mixed up with the old 'ISUP' leaving none of them working. This has also been fixed. The version number of the 'Smart' version of CIMA was increased to 3.1.04 after the fixes.

29 December 2008: Upgraded restart of chat window in remote sessions (Versions 3.0 and 3.1)

The automatic restart of a closed or killed chat window in CIMA version 3.1 (called 'smart') has been improved to be more reliable. The normal version of CIMA (version 3.0) has been upgraded to include the same code. The CIMA version numbers were increased to 3.0.10 and 3.1.02 after the upgrade.

22 December 2008: Restart of chat window in remote sessions (Version 3.1)

The automatic restart of a closed or killed chat window has been implemented in the "smart" version of CIMA (3.1). If the chat window is closed or disappears, CIMA will restart it within 30 seconds. The CIMA version number was increased to 3.1.01 after the upgrade.

16 December 2008: CIMA version 3.1 (called "Smart") installed

Version 3.1 of CIMA called "Smart" has been officially released. Among the new features are better support of the Mock spectrometer for ALFA observations, some new options for the use of winking cal and continuous data taking for all spectral line observing modes, some new command file features as well as the new smart basketweaving observing mode. You can read about the new version here.

6 November 2008: WAPP software upgrade

The CIMA WAPP software was upgraded to remove several annoying warning messages. The WARNING messages for the duplicate AGC-data block and possible interpolations/extrapolations of the telescope position are now presented as INFO messages. Also, the chip count errors are only reported to the log file, unless they are larger than 5 samples. Another change was to allow the WAPP software to update the FITS-header keywords 'OBSMODE', 'SCANTYPE', 'PATTERN_ID' and 'SCAN_ID' dynamically during continuous data taking (a new capability that will be introduced in CIMA 3.1). The CIMA WAPP software called 'Dual' was renumbered to 1.4.15 after the upgrade.

27 October 2008: New default version of CIMA

The 'Normal' version of CIMA (version 2.2) has been renamed 'Old'. Version 'Next' (version 3.0) has become the new 'Normal' version. NOTE the incompatibility issues between version 3.0 and the previous versions of CIMA! Observers using 2.2 and earlier versions of CIMA are advised to consider the following four points: For further information, see this web page. All observers are strongly recommended to try out version 3.0 in off-line mode before using it on the telescope.

24 October 2008: Mock spectrometer upgrades (Version 3.0)

The 3.0 version of CIMA called 'Next' was upgraded to include some new Mock spectrometer options. Also, the protection that only allows access to the Mock spectrometer from 'x'-coded projects has been removed. The version number was increased to 3.0.06 after the upgrade.

21 October 2008: Polyco overflow bug fix (Version 2.2 and 3.0)

A bug has been found in CIMA that when using polyco files for pulsar folding, the last set sent from CIMA to the WAPPs may have all coefficients set to zero. Normally this set will be far in the future and never used, but if the polyco file contains multiple sets of polyco data for the same source, this set may get used. The bug has been fixed both in CIMA version 2.2 ('Normal') and 3.0 ('Next') and the version numbers where increased to 2.2.38 and 3.0.05 after the fix.

4 September 2008: CIMA bug fixes (Version 3.0)

Version 3.0 ('Next') of CIMA received a set of bug fixes. Among the bugs fixed where a fix to the problem that several incarnations of CIMA could be started for local on-line sessions while waiting for a remote session or a datataking session to finish, a modification to limit the WARNING beeps if a WAPP produces continuous chip count errors, modifications of the allowed range for some ALFA engineering parameters, as well as the correction of some pieces of code that could generate errors during special conditions. The version number was increased to 3.0.01 after the upgrade.

2 July 2008: Interim correlator configuration restoration bug (Version 2.2)

A modification to the CIMA executive scram block made on 7 December last year introduced a bug into the old version of CIMA (verison 2.2 'Normal') for observers using the interim correlator together with spider scan calibrations. Since the spider scan calibration modifies the frequency and interim correlator set-up, it is supposed to restore the user-selected configuration after the spider scan is finished. However, due to an allocation error, the number of lags for the fourth board is not stored correctly and thus the fourth board is not restored properly. Cross scan calibrations are not affected since CIMA is using the user-selected configuration for those ones. Also, the newer versions of CIMA (version 3.0 and recently removed 2.3) are not affected by this bug, and both spider and cross scan calibrations are restoring the interim correlator properly. (Note the difference for cross scans, since the newer versions modify the frequency and interim correlator set-up just like for spider scans while the older version doesn't.) The bug has now been fixed and the version number of the 'Normal' version of CIMA was increased to 2.2.33 after the upgrade.

2 July 2008: The 'Unusable' development version of CIMA removed (Version 2.3)

The development version of the next generation of CIMA (called version 2.3 'Unusable') has been removed since the official version (called 3.0 'Next') is available. Note that version 3.0 will ask You to select new preferences and will claim that configuration files created with version 2.3 are old. To upgrade Your configuration files, load them into CIMA, apply the configurations and then save a new copy of the configuration files.

26 June 2008: Longer time-out for ON-OFFs (Version 2.2)

The time-out for ON-OFF observations using the interim correlator have been increased to avoid problems of the time-out aborting observations using the radar blanker. The version number of the 'Normal' version of CIMA was increased to 2.2.32 after the upgrade.

12 June 2008: The next generation of CIMA officially installed

The next generation of CIMA (version 3.0 called 'Next') was officially installed today. It will replace the development version (version 2.3 called 'Unusable') that has been used for observations by a number of projects. Since all development of version 2.2 ('Normal') has (since long) been terminated, all observers are encouraged to migrate over to version 3.0, which will become the default version very soon, but do try it out off-line BEFORE getting on to the telescope to get familiar with it. The old version will be kept on-line for at least 6 months, maybe longer, to give all observers plenty of time to move over to the new version. The new version contains a lot of important modifications to make CIMA more robust, more reliable and easier to use. The improvements come with a price though: catalog files may need updating, command file syntax has changed and old configuration files can't be used - new ones have to be created with the new version. Some web pages have been updated to contain information on version 3.0 (2.3): the source catalog page, the preferences page, the configuration file page and the command file page.

17 April 2008: Proper 'Abort' command added to 'clear_cima' (Version 2.2)

An 'abort' command has been added to the clear_cima script, so that from now on clear_cima will send an abort command to CIMA and then wait 10 seconds for CIMA to shut down properly. This has become necessary since certain pulsar observers have got into a habit of leaving CIMA running and finishing their session by having the clear_cima script run to kill CIMA. While this surely kills CIMA, it doesn't tell the WAPPs to stop and there has been occasions when the following project has run into trouble because the WAPPs were still busy taking pulsar data. With the modification CIMA will be given enough time to stop the WAPPs and terminate the observing session properly. The 'abort' command is only sent when clear_cima is used to kill an on-line CIMA session. In the unlikely case that CIMA really is hanging and the attempt to send an 'abort' command prevents clear_cima from killing CIMA, the 'abort' command can be skipped by running clear_cima with the '-f' flag. The version number of the 'Normal' version of CIMA was increased to 2.2.28 after the upgrade.

1 April 2008: Padding modification in WAPP pulsar data files

The WAPP pulsar file writer has been modified so that the ASCII-part of the header always will be padded to an even 8-byte length, so that the rest of the file will be properly aligned on woprd boundaries.

1 April 2008: New 'wapp_split' program installed

A new program called 'wapp_split' has been installed on '/home/cima/bin'. This program is for pulsar observers who want to separate the two ALFA beams or the two dual board data streams from the WAPP pulsar files. It replaces the old '/share/wappsrc/utility/alfasplit' program that only can deal with ALFA dual board data.

10 January 2008: Old 'aostatus' disabled

The old version of 'aostatus' located at '/home/aoui/bin/aostatus' has been disabled. The new version is located at '/home/cima/bin/aostatus'. The 'aostatus' links from '/usr/local/bin' have been updated to point to the new version. If You have '/usr/local/bin' in Your path, You will get the new version automatically if You just type 'aostatus'.

7 December 2007: Compatibility upgrade of CIMA (Version 2.2)

The 'Normal' version of CIMA (version 2.2) has been upgraded to remain compatible with the modified CIMA WAPP software. The upgrades are required beacuse of syntax changes for some commands sent to the WAPPs, the modifications made to the WAPP pulsar headers, the rework of the SCRAM package broadcast by CIMA as well as the modification to VX-works, so that it now can handle all eight synthesizers. The 'hcorcal' is now the default calibration type in CIMA. The ALFA calibration types have been renamed from 'hcal' and 'lcal' to 'hcorcal' and 'lcorcal', respectively. The small text-based monitor has lost a bit of its functionality due to changes made to the SCRAM broadcasts. There has also been some modifications to make the 2.2 version compatible with some auxiliary programs that are going to be introduced in the new version of CIMA. The version number was increased to 2.2.22 after the upgrade.

7 December 2007: Move of 'aostatus'

The 'aostatus' program producing the big black display with observing information and a graphic display of the telescope has been moved into CIMA. The new code is located at '/home/cima/bin/aostatus'. The old code at '/home/aoui/bin/aostatus' is still available but will soon be removed. NOTE that the old code, no longer displays project-ID, source name, backend, scan number or seconds remaining. Also, the rest frequencies will be incorrect when CIMA is running.

4 October 2007: CIMA version 2.1 removed

The old CIMA version 2.1 which has been called 'old' has been removed.

5 April 2007: 610 MHz receiver removed (Versions 2.1 and 2.2)

The 610 MHz receiver option has been removed, since that receiver has been decommissioned. To reflect this change, the CIMA version numbers for the old and normal versions were increased to 2.1.25 and 2.2.19, respectively.

27 February 2007: DPS interim correlator Doppler correction (Version 2.2)

The Doppler calculation for the 'velocity(optical)' system when using dual position switching with the interim correlator was updated to include the second-order term as described by the PostScript document from 8 February below. Note that for dual position switching, Doppler calculations are done by CIMA, so the column for the interim correlator in this document does not apply. The CIMA version number was increased to 2.2.18 after the fix.

20 February 2007: WAPP pulsar file number bug corrected (Versions 2.1 and 2.2)

A bug in the procedure that determines the next file number to use for WAPP pulsar data files has been found that under certain circumstances would reuse the sequence number '0000' even if it had already been used. This has been corrected and the CIMA version numbers were increased to 2.1.24 and 2.2.17 after the fix.

8 February 2007: Doppler calculation for WAPP observations modified

The formulae used for Doppler calculations when observing with the WAPPs have been changed to include the second-order term that so far has been omitted (for a PostScript page with details, click here).

30 January 2007: CIMA version 2.0 removed

The old CIMA version 2.0 which has been called 'historic' has been removed.

22 December 2006: Filter options added for 327 MHz receiver (Version 2.2)

The possibility to select between two different filters (312-342 MHz and 302-352 MHz) has been added for the 327 MHz receiver. The CIMA version number was increased to 2.2.13 after this upgrade.

8 November 2006: WAPP software upgrades (all versions)

The spawners used to restart the WAPPs, GPIB or ALFA software have been modified to report if they can't find the programs to restart. This modification was made to handle instances of problems with NFS-mounted disks. Also, a new watch dog (called wapp_watch) has been installed on all WAPPs. This watch dog periodically checks if all parts of the WAPP software is running. The watch dog will report a WAPP failure and try to restart the WAPP, if some program has crashed. The CIMA WAPP software version number was increased to 1.2.05 after the upgrade. This change affects all CIMA versions, which needed a small modification to receive a new type of message from the watch dog. The CIMA version numbers for the historic, old and normal versions were increased to 2.0.09, 2.1.20 and 2.2.12, respectively.

1 November 2006: WAPP software upgrades (all versions)

For observing modes that involve telescope commands sent just before the data taking starts (without waiting for the telescope to report that it is tracking), the WAPPs have up until now produced warning messages saying that the telescope is not tracking regardless off whether it was true or not. The reason is that the telescope goes into 'Settle' mode for a number of seconds regardless of if it is already tracking the position or not, and the WAPPs have reported this as not being on source. This has now been changed so that the WAPPs check the current tracking error and compare it with the allowed tracking tolerance, thus only producing warning messages if there really is a reason for it. Also, the warning messages for large FITS-files have been corrected since the size reported by the FITS-writer was not correct. Both these changes were made in the CIMA WAPP software which had its version number increased to 1.2.04 after this upgrade. All CIMA versions will benefit from these modifications.

31 October 2006: Addition of GPIB and ALFA restart buttons (all versions)

Buttons to restart the GPIB socket communication as well as the ALFA control software have been added to the 'Utilities' menu in all CIMA versions. The GPIB restart capability should be used instead of the direct call to /home/cima/Wapp/Bin/Progs/Start/start_gpib. The CIMA version numbers for the historic, old and normal versions were increased to 2.0.08, 2.1.19 and 2.2.11, respectively.

11 October 2006: WAPP IF/LO set-up bug fix (Version 2.2)

It has been discovered that WAPP data taken with 100 MHz bandwidth may have been taken with the destination frequency incorrectly set to 275 MHz instead of 250 MHz when the set-up is done from a configuration file. The problem occur if You have used a .gui-file or a .iflo-file which contains the word "MHz" in the variables iflo(bwN) where 'N' is 0, 1, 2 or 3. It also occur if You have used a .wapp-file and done a reconfiguration of the IF/LO-setup AFTER You loaded the .wapp-file. This problem has been patched and the CIMA version number was increased to 2.2.10.

To see the full announcement, click here.

27 September 2006: WAPP pulsar file name fix (Version 2.2)

When run in pulsar mode, CIMA queries WAPP-1 for the sequence number for the next file. If the WAPPs would get out of synch for some reason so that there are files with higher sequence numbers on other WAPPs, CIMA will end up in a state where it is impossible to take any further data since those other WAPPs will complain about the sequence number being used. CIMA has now been modified to query all selected WAPPs to avoid this problem. The CIMA version number was increased to 2.2.09 after this fix.

5 July 2006: Raise of chat window (Version 2.2)

The chat window for remote observers has been modified so that it is raised on top of all other windows every time a new message arrives. The CIMA version number was increased to 2.2.06 after this upgrade.

23 June 2006: New default version of CIMA

The 'Normal' version of CIMA (version 2.1) has been renamed 'Old'. Version 'Capable' (version 2.2) has become the new 'Normal' version. The version called 'Old' (version 2.0) has been renamed 'Historic'.

23 June 2006: New basketweaving mode introduced (Version 2.2)

A new basketweaving mode has been introduced that runs in true Az/ZA coordinates. It uses the same interface as the old basketweave routine, and the observer selects which version to use with a new option. When using the new true Az/ZA mode, the 'Start RA' and 'RA rate' options are ignored. The new mode can only be run on the meridian. The CIMA version number was increased to 2.2.05 after this upgrade.

23 June 2006: Fix of cross calibration printing bug (Version 2.2)

The postscript file generated by the cross calibration routine contained a bad header which fooled the printer to print it as text wasting huge amounts of papaer. This bug has been fixed in version 2.2.05.

15 June 2006: Lastcimalog made more robust (Versions 2.1 and 2.2)

The lastcimalog program has been made more robust to avoid it from crashing or hanging if there are problems with the graphic display. The CIMA version numbers were increased to 2.1.18 and 2.2.04 after the upgrade.

9 June 2006: PULSARCATCALOBS offset bug (Version 2.2)

An early abort of PULSARCATCALOBS could leave a telescope offset in the system. This bug has been fixed and the CIMA version number was increased to 2.2.03 after this modification.

5 June 2006: Pulsar file name change (Version 2.2)

The scheme for file names for pulsar calibrations have been changed. So far the files have been named with the source name for the on-position and the source name with an added suffix like '_north' or '_east' for any offset position. This has been changed so that all calibration files regardless of whether they are taken on-source or off-source have the same name which is the source name with the suffix 'cal' added. The version number was increased to 2.2.01 after this modification.

25 May 2006: CIMA version 2.2 installed

A new version of CIMA has been installed. It is currently called 'capable' and its version number is 2.2. It includes the new ALFA sky angle tracking, several new observing modes and several new commands for command file observing as well as some minor additions and bug fixes. For a full description of all modifications, see the CIMA version log.

25 May 2006: CIMA version 1.2.03 removed

The old CIMA version 1.2.03 which has been called 'ancient' has been removed.

22 May 2006: Correction of quick look and ALFA log windows (Version 2.1)

The data quick look facility as well as the ALFA engineering log display have been using some internal Tcl/Tk code for configuring slide bars. This code is no longer available in Tcl/Tk 8.4. These two programs have been now been modified so that they can run under the newer version of Tcl/Tk as well. The CIMA version number has been increased to 2.1.15 after this fix.

9 May 2006: Move of remote chat window (Version 2.1)

The chat window for remote observers have been centered on the screen, sometimes hiding the CIMA start-up window for remote observers. The centering has been removed and the CIMA version number has been increased to 2.1.14.

9 May 2006: New command to watch the current CIMA log (Version 2.1)

A new command 'lastcimalog' has been added to the CIMA system. This command opens up a window similar to the log window shown while observing with CIMA. It is not showing the same things though, since this window reads what is written in the log-file. It thus provides more information than the regular observing log window. It can be used to monitor progress or trouble-shoot problems. This window has been added to the operators' console so that they can see the log when dealing with problems for remote observers.

8 May 2006: CIMA version 1.1.00 removed

Jeff's old version of CIMA which has been called version 1.1.00 'Original' has been removed.

24 April 2006: Emails sent from CIMA in off-line mode (Version 2.1)

CIMA has been upgraded so that you could send CIMA comments and RFI reports also from an off-line session running on a Linux machine. The version number was increased to 2.1.13 after the modification.

20 April 2006: Interim correlator abort and time-outs improved (Version 2.1)

The code for aborting the interim correlator was improved. Also, time-outs have been improved to deal with the radar blanker. The version number was increased to 2.1.12 after the modification.

12 April 2006: Two window bugs corrected (Version 2.1)

Two window bugs were corrected in CIMA version 2.1. One of them was to avoid CIMA to believe it was started as a remote session if it was launched from the right-hand screen on observer2. The other one was a window positioning command used in the telescope offset window that has caused problems for remote observers. The version number was increased to 2.1.11 after the modification.

11 April 2006: Frequency bug corrected (Version 2.1)

A bug that could make CIMA choose the wrong rest frequency for the WAPPs if it was far away from the center frequency has been corrected. The correction affects CIMA version 2.1 as well as the software running on the WAPPs. (Since this bug was technically speaking not part of CIMA but of the CIMA WAPP software, the version number of CIMA was not increased.)

22 March 2006: Snap available on dataview (all versions)

The pulsar quick-look facility snap can now be run on dataview. Up until now it has only been possible to run it on one of the WAPPs although there has been an entry for dataview in the pulsar menu.

16 March 2006: Telescope offset and pulsar observation bug fixes (Version 2.1)

Several bugs have been fixed in the 'normal' version of CIMA which had its version number increased to 2.1.09 after these modifications. Bugs related to the polyco-based folding and to the use of the 'PULSARCATOBS' command were fixed as well as bugs related to the selection of telescope pointing offsets. Pointing offsets are now removed whenever a new receiver is selected (which is not the case in older versions of CIMA). Also the button 'Clear offsets' will now actually tell the telescope to remove the offsets. In earlier versions of CIMA, the numbers in the menu were changed to zero but the observer then had to click on 'Apply telescope pointing offsets' to actually tell the telescope to remove the offsets.

7 February 2006: New default version of CIMA

The 'Normal' version of CIMA (version 2.0) has been renamed 'Old'. Version 'Evolved' (version 2.1) has become the new 'Normal' version. The version called 'Stable' (version 1.2.03) has been renamed 'Ancient'.

NOTE that the syntax has changed in version 2.1 for command file observing as well as for pulsar catalog observing (the latter has been merged with the command file observing). All command file observers should thus study the new CIMA command file observing page carefully and adapt their command files (pulsar catalog files) before using CIMA version 2.1.

6 February 2006: Restoration of velocity defaults (Version 2.1)

The change on 5 December 2005 to use the default values 'Topocentric' and 'velocity(optical)' for the velocity frame and velocity type if nothing is specified in the source file has been taken back when selecting sources interactively in the 'evolved' version of CIMA. Whatever selected in the pointing window will thus remain as the default whenever a new source is selected. The mentioned default values are, however, used when source files are read in command file mode, so any source file used for command file observing should thus have these parameters specified (unless the default is OK). The same rule also applies to standard ONs which use a source catalog. A number of warning messages were also added to the 'evolved' version which had its version number increased to 2.1.08 after these modifications.

18 January 2006: New Doppler options for RA/Dec and Dec/RA mapping (Version 2.1)

Two new options for Doppler correction of interim correlator RA/Dec and Dec/RA mapping were added: 'odd strips only' and 'even strips only'. At the same time the non-working option 'first strip' was removed. The CIMA version number for the 'evolved' version was increased to 2.1.07 after the upgrade.

16 January 2006: Basketweaving time limit removed (Version 2.1)

The limit in the basketweave routine that started observations immediately if the wait is more than 1 hour has been removed. The CIMA version number for the 'evolved' version was increased to 2.1.06 in this upgrade that also included adding a data flushing command to the 'Restart WAPP' sequence.

10 January 2006: CIMA mini-upgrade (Version 2.1)

A few modifications and some bug fixes were added to the 'evolved' version of CIMA which had its version number increased to 2.1.05. Two new commands for making command file observing with the interim correlator were added: ICORRCONFIG and NEWICORRFILE. An option to select filterbank for ALFA has been added (Note though that rxview, the graphic IF/LO set-up display, does not yet show the selected band). A couple of swapped labels in the basketweave menu have been corrected.

22 December 2005: CIMA mini-upgrade (Version 2.1)

A couple of modifications were added to the 'evolved' version of CIMA which had its version number increased to 2.1.04. Double Position Switching and the Run Correlator modes for the interim correlator could earlier only handle correlator cycle times (integration times) of 1 second. This has now been fixed. Error messages have been added to several other observing modes that can't handle interim correlator dump times less than 1 second (standard on, standard on/off, drift map and ephemeris tracking). There is now an 'Adjust Correlator Power' button in the back-end menu (replacing the old 'Adjust Power' button for WAPP since 'Adjust Power' is available from the observing menu). The difference between 'Adjust Power' and 'Adjust Correlator Power' is that the latter only adjusts the correlator power levels while the former also adjusts the power for IF1 and IF2. Observers who manually set up the IF1 and IF2 power levels should thus use the 'Adjust Correlator Power' button (and disable power adjustments in their observing mode). The preferences are now listed to the log file. The executive log window has been made wider, since many lines written to the log is longer than 80 characters.

14 December 2005: CIMA mini-upgrade (Version 2.1)

Several modifications were added to the 'evolved' version of CIMA which had its version number increased to 2.1.03. The WAPP power levels are now written to the log when the power is adjusted. A new command has been added for command file observing: GOTO. The GOTO command sends the telescope to a source without waiting for it to reach the source. Options for selecting filterbank for the 430 MHz Greogorian receiver has been added. Two new options have been added to fixed azimuth drift maps: a velocity and a velocity frame specification. The veolcity type for fixed azimuth drift maps is hard-coded to be 'velocity(optical)'. Also the tracking command for this observing mode is now sent before the ALFA rotation command to allow them to run in parallel.

5 December 2005: Velocity defaults added for source lists (Version 2.1)

The parameters velocity frame and velocity type was never read from the source file in pulsar mode. These values were instead hard-coded to 'Topocentric' and 'velocity(optical)'. This has now been changed so that these values are default values to be used if the source file does not contain any explicit velocity frame and velocity type. This change also affects spectral line observing since these defaults, as well as a default velocity of zero, now are applied automatically whenever the information is not given in the source file. Earlier the previously set values were just retained in spectral line mode. The version number was increased to 2.1.02 after this modification. NOTE: users of values other than 'Topocentric' and 'velocity(optical)' who don't have specified the velocity frame and velocity type in their catalog files probably want to add those values to their catalogs to avoid having to reselect them when changing source. (See entry for 6 February 2006 for further modifications.)

5 December 2005: News when selecting CIMA version (all versions)

A news box is now shown when the CIMA selection menu comes up. This box contains some important pieces of information and recommendations on the selection of CIMA version. It is printed above the menu when 'cima --V' is used and below the menu in the graphical menu produced by 'cima --X'. The versions in the menu are now sorted in version order with the latest version coming first. Test versions are separated from the official versions by an empty line.

1 December 2005: CIMA mini-upgrade (Version 2.1)

A set of 12 modifications were added to the 'evolved' version of CIMA which had its version number increased to 2.1.01. The 'Dec/Ra' mapping mode now accepts the option to adjust the power before starting the mapping. The size of the interim correlator file is now shown in the observation status window. The size is also written to the log-file together with the file name whenever interim correlator data is moved to a new file. The azimuth and zenith angle is written to the log-file when a Tsys is made. The 'End' button that was renamed 'Break' with the introduction of version 2.1 has been renamed to 'Stop'. The spectral line observing menu now has the same six buttons both when the WAPPs and when the interim correlator is used. The two buttons 'Move data' and 'New FITS-file' have been merged to one button called 'New file'. A 'Stop' button has been added and there is now also an 'Adjust power' button for the interim correlator. Several important warning messages have been added to the system.

16 November 2005: CIMA version 2.1 installed

A new major revision of CIMA has been installed. It is currently called 'evolved' and has the version number 2.1. It includes a new command file observing facility, better support of the observation status window, improved busy and abort handling, better error handling as well as a number of bug fixes. For a full description of all modifications, see the CIMA version log.

23 October 2005: Multiple loop bug in smart frequency switching fixed (Version 2.0)

In CIMA version 2.0, the smart frequency switching would only run once even if it was asked to run several loops. This bug has been fixed and the version number has been increased to 2.0.06.

18 October 2005: 'Executive busy' changed to error message (Version 2.0)

The message given when the CIMA executive is busy has been changed from being a warning message to be an error message.

28 September 2005: IDL spider scan bug fixed (Version 2.0)

A bug that has prevented IDL graphics for spider scans to be displayed in CIMA version 2.0 has been fixed.

28 September 2005: ALFA parallactic angle bug fixed (Version 2.0)

A bug was found in one of the routines used to set the parallactic angle for ALFA. The incorrect routine did not precess coordinates before using them. This routine was used whenever an observer selected a parallactic angle from the 'Pointing' menu, the command file observing command 'PARAANGLE' and also by the ephemeris tracking observing mode. No other observing modes were affected. The version number has been increased to 2.0.05 after this bug was fixed.

20 September 2005: Option for IDL window added (Version 2.0)

A new option has been added to the preference menu which allows the observer to select whether the big IDL graphics window should be launched automatically when CIMA starts up or not. The default is currently 'Yes'. If this option is set to 'No', the IDL graphics window can be opened using the 'Enable Exec IDL' button in the 'IDL Control' menu found in the 'User Preferences' main menu. The version number has been increased to 2.0.04 after this addition.

19 September 2005: New default version of CIMA

The 'Normal' version of CIMA (version 1.2.03) has been renamed 'Stable'. Version 'Expanded' (version 2.0) has become the new 'Normal' version. The version called 'Older' (version 1.2.02) has been removed.

14 September 2005: False alarms for hanging observations (Version 2.0)

The alarm for hanging observations would give false alarms for standard pulsar observations. This has now been corrected for version 2.0.03.

23 August 2005: Incorrect restart commands in CIMA (Version 2.0)

The buttons in the 'User Preferences' menu to restart various parts of the CIMA system have been incorrect in the sense that they have not passed on all the information needed for the restart. The executive, for example, stopped writing to the log-files if it was restarted. This has now been corrected for version 2.0.01. The problem also exists in all earlier versions but is more benign for those versions.

23 August 2005: Change of version numbering scheme

The early versions of CIMA have unfortunately got version numbers which only differ in the third number (for example 1.2.02 and 1.2.03). From now on, starting with version 2.0.00, versions will only be referred to with the first two numbers (for example 2.0), while the third number will be incremented each time there is a modification to that version. An overall description of the differences between the different versions is given on the CIMA version log page, while all the details are given either on this page or on the CIMA engineering log or the CIMAFITS log pages.

6 July 2005: Fix of calibrator for interim correlator (Version 1.2.03 and 2.0.00)

Phil discovered that CIMA incorrectly sets up the 25 Hz cal for use when the interim correlator is selected. This has been corrected in the versions 1.2.03 and 2.0.00.

28 June 2005: CIMA version 2.0.00 installed

A new major revision of CIMA has been installed. It is currently called 'expanded' and has the version number 2.0.00. It includes a new observation status window, a new start-up sequence, new preferences, better error handling, new options to some observing modes, better logs, better support for off-line sessions as well as a number of bug fixes. For a full description of all modifications, see the CIMA version log.

The version of CIMA called 'Test' was removed since it was identical to the 'normal' version.

31 May 2005: CIMA version description window

A button called 'Show version descriptions' has been added to the CIMA version selection window. Clicking on this button will produce a help page with brief descriptions of the currently available versions of CIMA.

27 May 2005: Renaming of CIMA versions

The 'Normal' version of CIMA (version 1.2.02) has been renamed 'Older'. Version 'Test' (version 1.2.03) has become the new 'Normal' version.

25 May 2005: New directory for WAPP FITS-files (all versions)

The FITS-files generated by the WAPPs are now written to /share/pserverf.sdb1/wappdata instead of /share/pserverf.sda3/wappdata. However, the proper way to access the files is not to remember this new address but to use the generic address /share/wappdata that contains links to all FITS-files.

24 May 2005: Improved log messages (Version 1.2.03)

Log messages for several observing modes were improved, mostly for the end of an observation.

24 May 2005: Fix of synchronization for basketweave and drift chase modes (Version 1.2.03)

The fixes introduced on 22 February 2005 to correct for data timestamping bugs on the WAPPs broke the synchronisation between telescope movements and datataking with the WAPPs for two observing modes: 'basketweave' and 'drift chase'. This has now been corrected in the new version 1.2.03 of CIMA which currently is called 'test'. Users of these two modes should not use any CIMA version earlier than 1.2.03.

20 May 2005: Links to FITS-files (all versions)

The FITS-writer will now automatically put links in the directory /share/wappdata pointing to the FITS-files written in /share/pserverf.sda3/wappdata. The idea is that the user should be able to access his/her data via a standard directory (/share/wappdata) without having to know on which disk the data physically resides; this is important since data may be written to different physical disks depending on availability of disk space.

10 May 2005: Renaming of CIMA versions

The 'Normal' version of CIMA (version 1.1.00) has been renamed 'Original'. Version 'New' (version 1.2.02) has become the new 'Normal' version. The intermediate versions 'Improved' (version 1.2.00) and 'Test' (versions 1.2.01) have been removed. A new version 'Test' has been installed, currently being identical to the new 'Normal' (version 1.2.02).

10 May 2005: Correction of bug preventing use of user-defined lay-outs (all versions)

A bug that prevented user-defined lay-outs to be used in the quick-look and the ALFA data logger displays have been corrected in all versions of CIMA.

9 May 2005: Interim correlator driftmap improvement (Version 1.2.02)

Driftmaps taken with the interim correlator can now start on any strip - not just the first one as has been the case up until now.

9 May 2005: LST midnight roll-over bug (Version 1.2.02)

Several observing modes have been affected by a bug that can cause CIMA to think that it has to wait 24 hours before it can proceed during LST midnight roll-over. This bug is now fixed.

5 May 2005: Autoselection of correlator widget (Version 1.2.02)

CIMA has been improved to automatically select the proper correlator widget depending on whether ALFA has been selected or not. Users of ALFA will thus reach the correct widget directly when clicking on 'Backend Control'.

4 May 2005: New command file command 'WAPPCONFIG' (Version 1.2.02)

A new command file command WAPPCONFIG to configure the WAPPs have been added. This command has to be run after a LOADIF command. Also, the CIMA frontend windows for receiver and IF/LO set-up will now be updated when the LOADIF command is run.

2 May 2005: Improvement of command file observing (Version 1.2.02)

The command file line numbers reported while running a command file observation have been corrected. Each line executed from the file will also be echoed in the log window and the log file. The broken command NEWFITSFILE to generate a new FITS-file has been fixed.

2 May 2005: New buttons (Version 1.2.02)

Buttons to stop the telescope and to release it again have been added to the pointing widget. The 'Stop telescope' button can be used as an emergency stop to stop the telescope from moving. The telescope will start moving again when you select a new source from the pointing widget and press the Point button. Otherwise, use the 'Release telescope' button to release the telescope from being held - the telescope will then continue to where it was going when you stopped it. Buttons to adjust the power levels and start a new FITS-file have been added to all the spectral line observation widgets when the WAPP is used as the back-end.

29 April 2005: New pulsar galactic coordinate mapping mode (Version 1.2.02)

A new mapping mode for pulsar observations using galactic coordinates have been added, although it has not yet been fully tested.

27 April 2005: Different versions of ALFA fixed azimuth drift mapping merged (Version 1.2.02)

The three versions of the ALFA fixed azimuth drift map into one single version. The alternative versions located at /home/lerner: fixedAZ2_widget.tcl, fixedAZ2.tcl and j2000_drift.tcl are thus no longer needed.

26 April 2005: Comment widget fixed (Version 1.2.02)

The widget to write a comment directly to the CIMA log file has been corrected so that it always works. It used to work only when the executive was busy.

25 April 2005: Version numbers added to CIMA

Version numbers were added to the various CIMA versions. This will make it easier to keep track of which versions have a desired feature. Modifications introduced in an earlier version are always kept in all later versions unless something else is explicitly stated. Version selection is still done via the version names, but version names will change over time (i.e. a version called new now will most certainly be old half a year from now).

21 April 2005: Added interim correlator 0.5 second mode

A 0.5 second integration mode for the interim correlator has been added to the CIMA version 'test'. Also, the 30 second integration options for the WAPPs have been removed since it does not work properly.

18 April 2005: Fix of selections from lists in CIMA

A problem when selecting items from lists when CIMA is run off-line on computers with newer versions of Tcl/Tk have been fixed.

18 April 2005: New ephemeris tracking mode and new pulsar RA/Dec mapping mode added

The 'improved' version of CIMA contains two new observing modes: a pulsar RA/Dec mapping mode (similar to the already existing Az/ZA mapping mode) and the spectral line ephemeris tracking mode providing "Standard ONs" for a non-stationary source with proper Doppler correction and support of ALFA rotation. The ephemeris tracking should support both the WAPPs and the interim correlator, but the latter has not been properly tested.

18 April 2005: Move of CIMA

The CIMA observing interface previously located in /home/aoui/bin has been moved to /home/cima/bin. This will not really affect anyone, since most people usually launch CIMA either via a menu or by just typing 'cima' which invokes a symbolic link set up in /usr/local/bin. For Sun users the link used to be in /usr/S2local/bin, but has now been moved over to /usr/local/bin.

CIMA is now launched via the CIMA version selection system described below. Use 'cima --X' to interactively select which CIMA version to use or set up a default with the 'select_cima --X' command. When CIMA is launched from 'dtusr' on 'observer2' it will ignore any default setting and always ask for the version.

There are currently three CIMA versions available:

11 April 2005: Move of ALFA-related software

All ALFA-related software previously located in /home/aoui/alfa and /home/aoui/alfa/Test have been moved to /home/cima/bin. Links to most programs of interest to the normal user has been added to /usr/local/bin which means that most users don't have to bother about the path to the software any longer, but can just type the name of the program they want to start.

The following programs are available:

Note that all these programs are considered part of CIMA and are now run via the CIMA version selection system described below.

11 April 2005: Introduction of the CIMA version selection system

The CIMA version selection system has been introduced for the ALFA-related software describe above. This system allows you to choose between several versions of the programs (old stable, new test, some special set-up etc.). When starting a program using the CIMA version selection system, it will produce a few annoying lines saying:

You have not selected which version of CIMA You want to use.
I will thus select the 'normal' version of CIMA for You.
Use the command 'select_cima' to set up a default version of CIMA or use
one of the '--' options (use '--h' for help) to select a certain version.

As the annoying text indicates, running 'select_cima' or 'select_cima --X' allows you to select which version you want as your default version and will reduce the annoying message to a single line telling you which version you are using.

When running a command from the command line, you can specify which version you want to use by adding a proper argument. As an example:

The usage of '--' instead of just '-' for the selection arguments is to separate those general arguments (which all CIMA programs understand) from program specific arguments.

The main menu on 'dataview' has been changed, so that a window will pop up asking you for the version you want each time you select one of the programs, until you use 'select_cima' (or 'Select CIMA Version' in the menu) to select a default version. The only program in the menu that will always ask for a version regardless of whether you have selected a default or not is 'CIMA offline'.

Note though that the command 'cima' and the version of CIMA used on 'observer2' does not yet use the CIMA version selection system.

17 December 2004: Move of log-files

All log files from CIMA that previously have ended up in /home/aoui/develop/log have been moved to the new area /home/cima/Logs. The new area is divided into several subdirectories and the ones that are used as a replacement for /home/aoui/develop/log are CIMA_logs, Executive_logs, Rxview and Sysmon.

22 November 2004: New command file command 'PARAANGLE'

The command 'PARAANGLE angle' to set the parallactic angle for ALFA was added for command file observations.

18 November 2004: S-band narrow shutter control

The missing call to control the shutter for S-band narrow observations was added.

12 November 2004: Driftchase

The final version for driftchasing tried out by the ultra-deep people was installed.

31 October 2004: Correction of third leg in spider scans

The third leg in spider scans has not been set up correctly. Phil fixed the problem.

This page is administered by Prakash Atreya ( patreya (a) naic . edu ) and was last updated on 13 November 2012.