kis_tools issueshttps://gitlab.leibniz-kis.de/sdc/kis_tools/-/issues2020-07-16T10:22:43Zhttps://gitlab.leibniz-kis.de/sdc/kis_tools/-/issues/176LARS: Different FOV sizes2020-07-16T10:22:43ZCarl SchafferLARS: Different FOV sizes![image](/uploads/fde7268878b278a13098996e61979cce/image.png)
Are the different FOV sizes accounted for in the observation descriptions?![image](/uploads/fde7268878b278a13098996e61979cce/image.png)
Are the different FOV sizes accounted for in the observation descriptions?https://gitlab.leibniz-kis.de/sdc/kis_tools/-/issues/186GRIS Coordinates: Solar Rotation2021-05-11T08:31:58ZCarl SchafferGRIS Coordinates: Solar RotationWhen using the updated GRIS data, Morten and Adur were not 100 percent sure whether the coordinates specified in the WCS keywords for the slit kws were correct. Definitely check this and write down some evidence.
Also check:
- Blue and...When using the updated GRIS data, Morten and Adur were not 100 percent sure whether the coordinates specified in the WCS keywords for the slit kws were correct. Definitely check this and write down some evidence.
Also check:
- Blue and Red observations
- Multimap observations
- Sit and Stare
- Polarimetric observations
Steps:
1. Collect testing data
2. Implement plotting of the coverage over a concurrent HMI Image
3. Compare with image content
4. Document results somewhere, eg here on gitlabhttps://gitlab.leibniz-kis.de/sdc/kis_tools/-/issues/193BBI: extname needs incremental file number2020-07-16T10:07:01ZCarl SchafferBBI: extname needs incremental file numberExtname needs to have an incremented file number so that it is unique within the pointing runExtname needs to have an incremented file number so that it is unique within the pointing runBBI Publicationhttps://gitlab.leibniz-kis.de/sdc/kis_tools/-/issues/216coordinate validation: check with HEK and HFC2020-07-16T10:51:31ZCarl Schaffercoordinate validation: check with HEK and HFCChek whether our coordinates line up with common feature cataloguesChek whether our coordinates line up with common feature catalogueshttps://gitlab.leibniz-kis.de/sdc/kis_tools/-/issues/248gris targets: redundant vocabulary2021-02-11T17:36:34ZCarl Schaffergris targets: redundant vocabulary![image](/uploads/5323c1dd8286fbba786a89f50886f007/image.png)
The targets specified in the headers and or db are not consistent. e.g. `Emerging flux Region` and `Emerging Flux Reg.` need to be consolidated.
Full consolidation includes...![image](/uploads/5323c1dd8286fbba786a89f50886f007/image.png)
The targets specified in the headers and or db are not consistent. e.g. `Emerging flux Region` and `Emerging Flux Reg.` need to be consolidated.
Full consolidation includes:
* [ ] Check where the tag names originate
* [ ] Decide on a consistent naming convention
* [ ] Open issues regarding enforcing and documenting said scheme
* [ ] Fix the names in all datasets, starting at L0 headers
* [ ] Fix the names in the corresponding observation entrieshttps://gitlab.leibniz-kis.de/sdc/kis_tools/-/issues/278gris_header: FITS Liberator compatibility2021-05-03T08:02:02ZCarl Schaffergris_header: FITS Liberator compatibilityhttps://gitlab.leibniz-kis.de/sdc/kis_tools/-/issues/290IFU translation errors2021-11-11T22:34:30ZCarl SchafferIFU translation errorsI ran IFU splitting and translation this week.
there are a number of runs that didn't process correctly. A collection of logs form all runs categorized by error type can be found at `/dat/sdc/gris_ifu/results_run_20211108`
Overview:
``...I ran IFU splitting and translation this week.
there are a number of runs that didn't process correctly. A collection of logs form all runs categorized by error type can be found at `/dat/sdc/gris_ifu/results_run_20211108`
Overview:
```
array_dimensions 1
broken_split 1
error_counts.txt 1
illegal_float 3
index_error 6
missing_ff 2
no_commands 132
no_problems 337
slices_problem 2
slitcntr_not_set 38
```
The folder also contains the commands used to split the logs into these categories, albeit only a dump of the bash history.https://gitlab.leibniz-kis.de/sdc/kis_tools/-/issues/293gris/IFU instrument segmentation2021-11-14T21:36:34ZCarl Schaffergris/IFU instrument segmentationa lot of the gris and IFU files are problematic due to their names that could fit to either instrument.
e.g. IFU continuum correction files would be added to the GRIS database by default.
This ambiguity needs to be addressed.a lot of the gris and IFU files are problematic due to their names that could fit to either instrument.
e.g. IFU continuum correction files would be added to the GRIS database by default.
This ambiguity needs to be addressed.https://gitlab.leibniz-kis.de/sdc/kis_tools/-/issues/308Stepsize value might be wrong for old data2022-04-26T07:25:07ZCarl SchafferStepsize value might be wrong for old dataThe Cassda-Gui prints the following message on loading old datasets e.g. 20150603_008:
![image](/uploads/8a990cd860cc47c77c487519629b6bed/image.png)
This implies that the step size value in the header might not be correct. InvestigateThe Cassda-Gui prints the following message on loading old datasets e.g. 20150603_008:
![image](/uploads/8a990cd860cc47c77c487519629b6bed/image.png)
This implies that the step size value in the header might not be correct. Investigate