kis_tools issueshttps://gitlab.leibniz-kis.de/sdc/kis_tools/-/issues2022-04-21T10:45:08Zhttps://gitlab.leibniz-kis.de/sdc/kis_tools/-/issues/300Map Overplotting2022-04-21T10:45:08ZCarl SchafferMap OverplottingImplement map overplotting as composite maps with hm data.
Implemented in IFUFitsFile as example.
Will only be useful once map rotation has been solved.Implement map overplotting as composite maps with hm data.
Implemented in IFUFitsFile as example.
Will only be useful once map rotation has been solved.Carl SchafferCarl Schafferhttps://gitlab.leibniz-kis.de/sdc/kis_tools/-/issues/295add grepfits for full calib pipeline2021-11-19T17:41:46ZCarl Schafferadd grepfits for full calib pipelinecalibration settings retrieval can be largely improved using grepfits and get last l0:
```
echo $(for i in /instruments/gris/202*;do ./gris_l0_info.sh $i;done) > last_l0_file_per_run.txt
grepfits "IMGSYS WAVELENG MEASURE TARGET FILESTAT...calibration settings retrieval can be largely improved using grepfits and get last l0:
```
echo $(for i in /instruments/gris/202*;do ./gris_l0_info.sh $i;done) > last_l0_file_per_run.txt
grepfits "IMGSYS WAVELENG MEASURE TARGET FILESTAT EXPTIME" $(cat last_l0_file_per_run.txt ) |tee $(date '+%Y-%m-%d')_gris_l0_info.csv
```
the output file can then replace the file in `kis_tools.gris.resources` and be used to generate calibration settings.
The shell scripts have been added to `kis_tools.gris.calib_settings`https://gitlab.leibniz-kis.de/sdc/kis_tools/-/issues/292IFU previews become very large as GIFS2021-11-14T20:02:35ZCarl SchafferIFU previews become very large as GIFSSwitch to different format, a 300 step GIF ends up at around 60MB, not feasible for quick look loadingSwitch to different format, a 300 step GIF ends up at around 60MB, not feasible for quick look loadinghttps://gitlab.leibniz-kis.de/sdc/kis_tools/-/issues/287Add interface to gristagger2021-09-30T10:30:05ZCarl SchafferAdd interface to gristaggerthe gristagger utility in the bin folder is undocumented even though it's pretty useful. Add a cleaner interface based on the kis_tools interface structure and add documentation.the gristagger utility in the bin folder is undocumented even though it's pretty useful. Add a cleaner interface based on the kis_tools interface structure and add documentation.https://gitlab.leibniz-kis.de/sdc/kis_tools/-/issues/284integrate test reports into gitlab2021-08-23T13:29:21ZCarl Schafferintegrate test reports into gitlabGitlab can parse error reports from unittest xml reports
See here for a manual:
https://gitlab.leibniz-kis.de/help/ci/unit_test_reports#how-to-set-it-upGitlab can parse error reports from unittest xml reports
See here for a manual:
https://gitlab.leibniz-kis.de/help/ci/unit_test_reports#how-to-set-it-uphttps://gitlab.leibniz-kis.de/sdc/kis_tools/-/issues/250mapgen: IQUV previews2020-10-16T09:49:51ZCarl Schaffermapgen: IQUV previewsAdd QUV previews to GRISAdd QUV previews to GRIShttps://gitlab.leibniz-kis.de/sdc/kis_tools/-/issues/246BBI observation sorting2020-09-25T09:12:15ZCarl SchafferBBI observation sortingProof of concept and first runs has been done, production code isn't readyProof of concept and first runs has been done, production code isn't readyhttps://gitlab.leibniz-kis.de/sdc/kis_tools/-/issues/245comon entry point for all fits files2022-03-15T07:55:47ZCarl Schaffercomon entry point for all fits filesImplement a common for all fits files, something like:
`open_kis_fits(filename) -> any of {GrisFitsFile, ChroTelFitsFile, BBI...)`
* [ ] add documentation about this to the base README.mdImplement a common for all fits files, something like:
`open_kis_fits(filename) -> any of {GrisFitsFile, ChroTelFitsFile, BBI...)`
* [ ] add documentation about this to the base README.mdhttps://gitlab.leibniz-kis.de/sdc/kis_tools/-/issues/242kis_tools git info2020-09-21T11:06:28ZCarl Schafferkis_tools git infoIf KIS tools is installed locally, it is impossible to update git_info dynamically. I need to either remove it or check it in at each commit.
Even better: add the generation to the install script and add it to MANIFEST.inIf KIS tools is installed locally, it is impossible to update git_info dynamically. I need to either remove it or check it in at each commit.
Even better: add the generation to the install script and add it to MANIFEST.inCarl SchafferCarl Schafferhttps://gitlab.leibniz-kis.de/sdc/kis_tools/-/issues/240WCS: Use programmatic building approach2021-09-02T07:39:14ZCarl SchafferWCS: Use programmatic building approachhttps://docs.astropy.org/en/stable/wcs/
provides a nice programatic approach for building wcs coords and generating the header keywords. Use this instead of the semi manual method from headershttps://docs.astropy.org/en/stable/wcs/
provides a nice programatic approach for building wcs coords and generating the header keywords. Use this instead of the semi manual method from headershttps://gitlab.leibniz-kis.de/sdc/kis_tools/-/issues/236translate_header: folder_out not working2021-09-02T07:26:41ZCarl Schaffertranslate_header: folder_out not working# Bug Report
Folder out option of `gris_translate_header` doesn't do anything, remove# Bug Report
Folder out option of `gris_translate_header` doesn't do anything, removehttps://gitlab.leibniz-kis.de/sdc/kis_tools/-/issues/224add logger2020-09-28T11:01:38ZCarl Schafferadd loggerremove importer utilitieshttps://gitlab.leibniz-kis.de/sdc/kis_tools/-/issues/207module: header tools2020-07-16T10:14:48ZCarl Schaffermodule: header toolsWrite a module that provides header checking from templates as well as well as eventually header generation for different instruments.
Should have different tests such as:
* [ ] Compare planned list of keywords to actual list of keywo...Write a module that provides header checking from templates as well as well as eventually header generation for different instruments.
Should have different tests such as:
* [ ] Compare planned list of keywords to actual list of keywords
* [ ] Check typing of values
* [ ] Check FITS comment lenghts in templates
* [ ] Host definitive templates for different instrumentshttps://gitlab.leibniz-kis.de/sdc/kis_tools/-/issues/174Coordinates: Querying2020-07-16T10:02:26ZCarl SchafferCoordinates: QueryingAll observations have a certain extent on the solar disk and should therefore not be queried only by their center, but queriable in a standard geographical way with intersects and containsAll observations have a certain extent on the solar disk and should therefore not be queried only by their center, but queriable in a standard geographical way with intersects and containshttps://gitlab.leibniz-kis.de/sdc/kis_tools/-/issues/154generic client filetype handling2020-04-21T16:46:35ZCarl Schaffergeneric client filetype handlingAllow SDCMongoClient to write filetype-specific entries to gridfs. Eg. add header of fits files, or specify image dimensions for image files.Allow SDCMongoClient to write filetype-specific entries to gridfs. Eg. add header of fits files, or specify image dimensions for image files.https://gitlab.leibniz-kis.de/sdc/kis_tools/-/issues/145add sharding before writing2019-07-17T13:49:53ZCarl Schafferadd sharding before writingWe want to shard all gridfs chunks collections between the different servers, this implies that before being filled with data, sharding needs to be activated for these collections. Some sample code implementing this is in [readHeader.py]...We want to shard all gridfs chunks collections between the different servers, this implies that before being filled with data, sharding needs to be activated for these collections. Some sample code implementing this is in [readHeader.py](lars/readHeader.py), lines 106 onwards, @guenter knows how it works.
This functionality could be implemented as a `create_gridfs(collection_name, activate_sharding=True)` method in SDCMongoClient which is then called in the `__init__` functions of inheriting classesPut good data on Websitehttps://gitlab.leibniz-kis.de/sdc/kis_tools/-/issues/155feature: generate location preview from header2021-04-27T07:54:43ZCarl Schafferfeature: generate location preview from headerEven if the coordinates in a header are not correct, they give a rough estimate to the location and could be used to provide a location preview even if there is no cross correlation. This location preview should show e.g. with error bars...Even if the coordinates in a header are not correct, they give a rough estimate to the location and could be used to provide a location preview even if there is no cross correlation. This location preview should show e.g. with error bars how large the uncertainty of the pointing is.https://gitlab.leibniz-kis.de/sdc/kis_tools/-/issues/120CI add testing as CI step2020-10-16T09:52:32ZCarl SchafferCI add testing as CI stephttps://gitlab.leibniz-kis.de/sdc/kis_tools/-/issues/239mapgen: plot in HPC2020-10-16T09:52:20ZCarl Schaffermapgen: plot in HPCGenerate maps in helioprojective coordinates instead of pixel coords unse Sunpy Maps for thisGenerate maps in helioprojective coordinates instead of pixel coords unse Sunpy Maps for thishttps://gitlab.leibniz-kis.de/sdc/kis_tools/-/issues/103headers: add observer2019-11-07T15:27:45ZCarl Schafferheaders: add observerAdd observer to headers. A csv file at headers/observers.csv containing the data has already been added. The entries are still too long to fit into the header and it is unclear who should be the main observer for each observation. Add observer to headers. A csv file at headers/observers.csv containing the data has already been added. The entries are still too long to fit into the header and it is unclear who should be the main observer for each observation.