|
⇤ ← Revision 1 as of 2008-04-24 14:14:15
Size: 1473
Comment:
|
Size: 1400
Comment:
|
| Deletions are marked like this. | Additions are marked like this. |
| Line 1: | Line 1: |
| == X-HSPOT How-To == | == X-HSPOT Features and BUGS == |
| Line 3: | Line 3: |
| X-HSPOT is far from perfect. it has features and BUGs. | '''USE 3.4.4 HSPOT release''' |
| Line 7: | Line 7: |
| it cannot deal with variables which content contains spaces: well known issue for us is the | ---- '''Obsolete''' * it cannot deal with variables which content contains spaces: well known issue for us is the |
| Line 9: | Line 11: |
| ---- | |
| Line 10: | Line 13: |
| It has been fixed in the PV scripts. | * Spaces are accepted in X-HSPOT: PLEASE use new HSPOT release: 3.4.4 |
| Line 12: | Line 15: |
| lines added: | |
| Line 14: | Line 16: |
| in the CUS signature: `string flt = “POS_A” in [“POS_A”,”POS_B”];` | * X-HSPOT does not know the difference between no_pointing and standard pointings commands (i.e. `PacsEng` or `PacsCal`): i.e. you must define a RA and DEC in the target panel on XHSPOT and give it a name even for the `PacsEng` AORs (shall be fixed in next build). |
| Line 16: | Line 18: |
| in the cus script body: `if ( flt == “POS_A” ) {string fltPOS = “POS A”;} else {if ( flt == “POS_B” ) {fltPOS = “POS B” ;}}` there is no indication this will be fixed anytime soon. X-HSPOT does not know the difference between no_pointing and standard pointings commands (i.e. `PacsEng` or `PacsCal`): i.e. you must define a RA and DEC in the target panel on XHSPOT and give it a name even for the `PacsEng` AORs (shall be fixed in next build). |
* -1 now is accepted as default value |
| Line 27: | Line 24: |
| IMPORTANT: give it a meaningful title | * IMPORTANT: give it a meaningful title |
| Line 29: | Line 26: |
| you should had an abstract | * you should had an abstract |
| Line 31: | Line 28: |
| IMPORTANT you have to attach a PDF file (still not sorted for the CAL): it does not need to be a “true” file, just use any PDF file or even (I checked) in the command line on your system (UNIX/Linux/ MAC) touch filename.pdf. It is enough. | * IMPORTANT you have to attach a PDF file (still not sorted for the CAL): it does not need to be a “true” file, just use any PDF file or even (I checked) in the command line on your system (UNIX/Linux/ MAC) touch filename.pdf. It is enough. |
| Line 33: | Line 30: |
| When hitting the submit button you will be asked a username and a password: Give your real name for traceability. “A” password has to be given, whichever, it is irrelevant. | * When hitting the submit button you will be asked a username and a password: Give your real name for traceability. “A” password has to be given, whichever, it is irrelevant. |
| Line 35: | Line 32: |
| In the Database, the AORs will be called Calibration_username_runingnumber | * In the Database, the AORs will be called Calibration_username_runingnumber ---- Please refer to the viewgrahs released by Sarah: http://www.herschel.be/twiki/bin/view/Hcss/ExpertUpdate |
X-HSPOT Features and BUGS
USE 3.4.4 HSPOT release
BUGS:
Obsolete
- it cannot deal with variables which content contains spaces: well known issue for us is the
“POS A”/”POS B” filter position.
- Spaces are accepted in X-HSPOT: PLEASE use new HSPOT release: 3.4.4
X-HSPOT does not know the difference between no_pointing and standard pointings commands (i.e. PacsEng or PacsCal): i.e. you must define a RA and DEC in the target panel on XHSPOT and give it a name even for the PacsEng AORs (shall be fixed in next build).
- -1 now is accepted as default value
Features:
to submit your proposal:
- IMPORTANT: give it a meaningful title
- you should had an abstract
- IMPORTANT you have to attach a PDF file (still not sorted for the CAL): it does not need to be a “true” file, just use any PDF file or even (I checked) in the command line on your system (UNIX/Linux/ MAC) touch filename.pdf. It is enough.
- When hitting the submit button you will be asked a username and a password: Give your real name for traceability. “A” password has to be given, whichever, it is irrelevant.
- In the Database, the AORs will be called Calibration_username_runingnumber
Please refer to the viewgrahs released by Sarah: