kis_tools issueshttps://gitlab.leibniz-kis.de/sdc/kis_tools/-/issues2019-05-02T15:28:18Zhttps://gitlab.leibniz-kis.de/sdc/kis_tools/-/issues/118WCS/coords: correlation color2019-05-02T15:28:18ZCarl SchafferWCS/coords: correlation colorThe keyword `STEPANGL` is not consistent with the correlation color of the run. We need another mechanism to get this property. Currently we are using hand-tagged correlation color by Ikrima. See below the difference in the step angle in...The keyword `STEPANGL` is not consistent with the correlation color of the run. We need another mechanism to get this property. Currently we are using hand-tagged correlation color by Ikrima. See below the difference in the step angle in the header and the values tagged by Ikrima. The numbers are the counts of the corresponding values, the difference in sums is due to missing values in both lists.
![image](/uploads/3a733d28e854ce40c4e7be161ba543c2/image.png)
@morten any ideas? Maybe we can incorporate it into the cross correlation saves in the future and update the save files with what we have from Ikrima?Put good data on Websitehttps://gitlab.leibniz-kis.de/sdc/kis_tools/-/issues/124coordinate_correction: solidify2019-05-13T13:34:07ZCarl Schaffercoordinate_correction: solidifyAll basic elements for coordinate correction are there, they now need to be consolidated into a useable toolAll basic elements for coordinate correction are there, they now need to be consolidated into a useable toolPut good data on Websitehttps://gitlab.leibniz-kis.de/sdc/kis_tools/-/issues/41convert solarx and solary to WCS2019-05-13T14:51:36ZCarl Schafferconvert solarx and solary to WCSPut good data on Websitehttps://gitlab.leibniz-kis.de/sdc/kis_tools/-/issues/134WCS-generator: Add header comments2019-05-31T14:39:32ZCarl SchafferWCS-generator: Add header commentsThere are currently no comments in the WCSkw section generated by the WCS-generatorThere are currently no comments in the WCSkw section generated by the WCS-generatorPut good data on Websitehttps://gitlab.leibniz-kis.de/sdc/kis_tools/-/issues/127correct coordinates2019-06-05T13:04:16ZCarl Schaffercorrect coordinatesPut good data on WebsiteCarl SchafferCarl Schafferhttps://gitlab.leibniz-kis.de/sdc/kis_tools/-/issues/117WCS/header2019-06-05T13:05:57ZCarl SchafferWCS/headerHandle Spec data: If no STOKES axis is defines, add one with a constant polHandle Spec data: If no STOKES axis is defines, add one with a constant polPut good data on Websitehttps://gitlab.leibniz-kis.de/sdc/kis_tools/-/issues/116WCS/header: Naxis4 not in header2019-06-05T13:06:41ZCarl SchafferWCS/header: Naxis4 not in headerMake sure that all kws from the Template are initialized in the header when the transformation is done
**or**: Apply coordinate transformation before header translation and set all the Keywords to 'keep'Make sure that all kws from the Template are initialized in the header when the transformation is done
**or**: Apply coordinate transformation before header translation and set all the Keywords to 'keep'Put good data on Websitehttps://gitlab.leibniz-kis.de/sdc/kis_tools/-/issues/131importer: add upload date2019-06-05T13:07:57ZCarl Schafferimporter: add upload dateadd upload date to importeradd upload date to importerPut good data on Websitehttps://gitlab.leibniz-kis.de/sdc/kis_tools/-/issues/125re-split2019-06-24T13:59:04ZCarl Schafferre-splitre split all level1 datare split all level1 dataPut good data on Websitehttps://gitlab.leibniz-kis.de/sdc/kis_tools/-/issues/92headers: coordinate uncertainties2019-06-24T14:00:00ZCarl Schafferheaders: coordinate uncertaintiesfill solar x and y coordinate uncertainties to one disk diameter, as the only thing we are sure of is that we are pointing at the solar disk for those observation runs where we have no cross correlation of the gris coordinates. For the r...fill solar x and y coordinate uncertainties to one disk diameter, as the only thing we are sure of is that we are pointing at the solar disk for those observation runs where we have no cross correlation of the gris coordinates. For the runs where a correlation is possible, we need to figure out a different method of estimating the uncertainty.Put good data on Websitehttps://gitlab.leibniz-kis.de/sdc/kis_tools/-/issues/132observation_reference: where to store2019-07-02T07:16:23ZCarl Schafferobservation_reference: where to storeWhere should the reference to an observation be stored in the gridfs files?
Currently there are two ways we do it:
![Selection_035](/uploads/089f9ec522d14e4f297a64d1a76b6982/Selection_035.png)
and:
![Selection_036](/uploads/90755835...Where should the reference to an observation be stored in the gridfs files?
Currently there are two ways we do it:
![Selection_035](/uploads/089f9ec522d14e4f297a64d1a76b6982/Selection_035.png)
and:
![Selection_036](/uploads/907558352e56ca76fedb0c63dd1191ca/Selection_036.png)
One of these or a mixture eg:
- file document
- obs_id
Should be the standard
Also these standards should be written down, stored and ideally used for building the entriesPut good data on Websitehttps://gitlab.leibniz-kis.de/sdc/kis_tools/-/issues/126update headers2019-07-02T07:17:57ZCarl Schafferupdate headersPut good data on Websitehttps://gitlab.leibniz-kis.de/sdc/kis_tools/-/issues/122gmc: remove defaults for host2019-07-02T07:22:28ZCarl Schaffergmc: remove defaults for hostPut good data on Websitehttps://gitlab.leibniz-kis.de/sdc/kis_tools/-/issues/111importer generic: add upload date to documents written to collections2019-07-02T07:31:41ZCarl Schafferimporter generic: add upload date to documents written to collectionsUpload dates are helpful for debugging and inspecting data. [lars importer](lars/LarsMongoClient.py) already does this. Move that code to genericUpload dates are helpful for debugging and inspecting data. [lars importer](lars/LarsMongoClient.py) already does this. Move that code to genericPut good data on Websitehttps://gitlab.leibniz-kis.de/sdc/kis_tools/-/issues/141gris_importer only one fits file per run2019-07-08T09:06:51ZCarl Schaffergris_importer only one fits file per run# Bug Report
## Summary
After reimporting the translated headers, only one fits file is stored in the DB per run
## Steps to Reproduce
import any run
## Expected Results
many files
## Actual Results
one file# Bug Report
## Summary
After reimporting the translated headers, only one fits file is stored in the DB per run
## Steps to Reproduce
import any run
## Expected Results
many files
## Actual Results
one filePut good data on Websitehttps://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/123reimport data with SOLARNET headers2019-07-23T11:59:20ZCarl Schafferreimport data with SOLARNET headersPut good data on Website