Size: 230
Comment:
|
Size: 1538
Comment:
|
Deletions are marked like this. | Additions are marked like this. |
Line 1: | Line 1: |
'''The entries below describe the OBS modules currently in the PV database.''' | This page will descripbe the BUGs and Features of Expert HSPOT: |
Line 3: | Line 3: |
[wiki:Self:PACS/CUSPVscripts/PacsEng_SPEC_prologue SPEC orbit prologue] | == X-HSPOT How-To == |
Line 5: | Line 5: |
[wiki:Self:PACS/CUSPVscripts/PacsEng_PHOT_prologue PHOT orbit prologue] | X-HSPOT is far from perfect. it has features and BUGs. === BUGS: === it cannot deal with variables which content contains spaces: well known issue for us is the “POS A”/”POS B” filter position. It has been fixed in the PV scripts. lines added: in the CUS signature: `string flt = “POS_A” in [“POS_A”,”POS_B”];` 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). === 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 |
This page will descripbe the BUGs and Features of Expert HSPOT:
X-HSPOT How-To
X-HSPOT is far from perfect. it has features and BUGs.
BUGS:
it cannot deal with variables which content contains spaces: well known issue for us is the “POS A”/”POS B” filter position.
- It has been fixed in the PV scripts.
- lines added:
in the CUS signature: string flt = “POS_A” in [“POS_A”,”POS_B”];
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).
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