sdc issueshttps://gitlab.leibniz-kis.de/groups/sdc/-/issues2020-07-16T11:04:49Zhttps://gitlab.leibniz-kis.de/sdc/issue_collection/-/issues/24ChroTel: Old Data2020-07-16T11:04:49ZCarl SchafferChroTel: Old DataThere is old ChroTel data stored at
/archive/chrotel/old/fits/:
```
(sdc) [12:25 schaffer@itchy 23] $ ls /archive/chrotel/old/fits/
2009 2010 2011 2012 index
```
The individual files are formatted differently than the data from 20...There is old ChroTel data stored at
/archive/chrotel/old/fits/:
```
(sdc) [12:25 schaffer@itchy 23] $ ls /archive/chrotel/old/fits/
2009 2010 2011 2012 index
```
The individual files are formatted differently than the data from 2012 onwards, Importing this data would require some further adaptions to `kharon`. It is currently not suited to deal with the data. Also the quality tagging won't recognize the files as the distribution and image quality are substantially different.
Sample of `ds9 HA_20090123_155356.fit.gz`:
![Selection_149](/uploads/d3f4664ef3232de7d421a4d124aedcb2/Selection_149.png)https://gitlab.leibniz-kis.de/sdc/issue_collection/-/issues/23GJSC Header: Coordinates2020-07-16T11:02:59ZCarl SchafferGJSC Header: CoordinatesAs coordinates are not available for SJC at the time. I propose to add dummy coordinates pointing to disk center with a high uncertainty value covering the entire disk. This way we can use tools that expect a well-formatted header. the `...As coordinates are not available for SJC at the time. I propose to add dummy coordinates pointing to disk center with a high uncertainty value covering the entire disk. This way we can use tools that expect a well-formatted header. the `CSYERRi` keyword can represent this state.
## Example:
```
CUNIT1 = 'arcsec ' / unit of axis 1
CDELT1 = 0.05 / [arcsec] step width per pixel
CTYPE1 = 'Angle HPC-LAT' / coordinate 1 is helioprojective latidude
CRVAL1 = 0 / [arcsec] offset of reference pixel
CRPIX1 = 1024 / reference pixel for axis 1
CSYER1 = 500 / Systematic Error along axis 1
CUNIT2 = 'arcsec ' / unit of axis 2
CDELT2 = 0.05 / [arcsec] step width per pixel
CTYPE2 = 'Angle HPC-LON' / coordinate 2 is helioprojective longitude
CRVAL2 = 0 / [arcsec] offset of reference pixel
CSYER2 = 500 / Systematic Error along axis 2
CRPIX2 = 1024 / reference pixel for axis 2
CUNIT3 = 's ' / units for time coordinate
CTYPE3 = 'UTC ' / coordinate 3 is time
CRVAL3 = 0 / [s] offset of reference pixel
CRPIX3 = 1 / reference pixel for axis 3
```https://gitlab.leibniz-kis.de/sdc/issue_collection/-/issues/22GSJC header: add OBS_MODE2020-07-16T11:02:43ZCarl SchafferGSJC header: add OBS_MODEAdding `OBS_MODE` makes data processing easierAdding `OBS_MODE` makes data processing easierhttps://gitlab.leibniz-kis.de/sdc/issue_collection/-/issues/21GSJC header: OBSGEO2020-07-16T11:02:24ZCarl SchafferGSJC header: OBSGEOObsgeo points to Roque de los muchachos. Correct coordinates are:
```
OBSGEO-X= 5385613.45 / [m] X coordinate of Cartesian triplet
OBSGEO-Y= 2900071.96 / [m] Y coordinate of Cartesian triplet
OBSG...Obsgeo points to Roque de los muchachos. Correct coordinates are:
```
OBSGEO-X= 5385613.45 / [m] X coordinate of Cartesian triplet
OBSGEO-Y= 2900071.96 / [m] Y coordinate of Cartesian triplet
OBSGEO-Z= -1800986.55 / [m] Z coordinate of Cartesian triplet
```
see https://gitlab.leibniz-kis.de/sdc/kis_tools/issues/219 for more infos.https://gitlab.leibniz-kis.de/sdc/chroquest/-/issues/16needs re-training2020-07-16T10:50:40ZCarl Schafferneeds re-traininghttp://localhost:8080/sdc/SDCDetailServlet?Instrument=chrotel&ObjectId=5ed04541b7af5756737309e2
http://localhost:8080/sdc/SDCDetailServlet?Instrument=chrotel&ObjectId=5ed04419b7af575673730932
http://localhost:8080/sdc/SDCDetailServlet?...http://localhost:8080/sdc/SDCDetailServlet?Instrument=chrotel&ObjectId=5ed04541b7af5756737309e2
http://localhost:8080/sdc/SDCDetailServlet?Instrument=chrotel&ObjectId=5ed04419b7af575673730932
http://localhost:8080/sdc/SDCDetailServlet?Instrument=chrotel&ObjectId=5ed04513b7af57567373099b
http://localhost:8080/sdc/SDCDetailServlet?Instrument=chrotel&ObjectId=5ed04317b7af5756737308e4
Some Helium images with clouds are not tagged correctly.https://gitlab.leibniz-kis.de/sdc/issue_collection/-/issues/18GRIS: Old data2020-07-16T10:31:54ZCarl SchafferGRIS: Old dataThere is old GRIS data in `/dat/sdc/gris/old_scans` we should asess whether we can incorporate that data or if we want to throw it out.There is old GRIS data in `/dat/sdc/gris/old_scans` we should asess whether we can incorporate that data or if we want to throw it out.https://gitlab.leibniz-kis.de/sdc/kis_headers/-/issues/4validate header should raise an exception instead of returning none2020-07-16T10:30:10ZCarl Schaffervalidate header should raise an exception instead of returning none@yakobchuk
I think `validate_header` should raise an error instead of a warning if you try to validate a header for an unknown instrument. I think it's okay to fail hard here because the function simply can't o anything if it doesn't kn...@yakobchuk
I think `validate_header` should raise an error instead of a warning if you try to validate a header for an unknown instrument. I think it's okay to fail hard here because the function simply can't o anything if it doesn't know what to check for. In this case it should fail spectacularly instead of returning `None` and exiting quietly... In the latter case it's pretty hard to track down the bug.
o something like: `RaiseNotImplementedError("The instrument [NAME] is not implemented here yet")` should do the trick.https://gitlab.leibniz-kis.de/sdc/kis_headers/-/issues/2header template for gsjc2020-07-16T10:28:28ZCarl Schafferheader template for gsjcnot that urgent but necessary at some pointnot that urgent but necessary at some pointhttps://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/chroquest/-/issues/5skew and kurtosisi as features?2020-07-16T10:15:28ZCarl Schafferskew and kurtosisi as features?https://gitlab.leibniz-kis.de/sdc/issue_collection/-/issues/9Outreach2020-07-16T10:09:52ZCarl SchafferOutreachCollection of Topics to think about for advertising SDC:
- Advertise SDC via different channels
- Judith's update on the website
- Credits for Lars
- basic Entry on Website:
- Projects -> Science Data Centre
- Provide Links, describe ...Collection of Topics to think about for advertising SDC:
- Advertise SDC via different channels
- Judith's update on the website
- Credits for Lars
- basic Entry on Website:
- Projects -> Science Data Centre
- Provide Links, describe plans, describe existing developmentshttps://gitlab.leibniz-kis.de/sdc/issue_collection/-/issues/8GRIS: Masks inconsistent2020-07-16T10:05:23ZCarl SchafferGRIS: Masks inconsistentThe masks for GRIS are inconsistent, sometimes -1 is used for artifacts, sometimes for small pores or similar features.
![Selection_089](/uploads/d42f9821a8254b9e2ce8061d3dae68db/Selection_089.png)
![Selection_092](/uploads/9bdbfcaea8ac...The masks for GRIS are inconsistent, sometimes -1 is used for artifacts, sometimes for small pores or similar features.
![Selection_089](/uploads/d42f9821a8254b9e2ce8061d3dae68db/Selection_089.png)
![Selection_092](/uploads/9bdbfcaea8ac91a810f13bfe7a4476db/Selection_092.png)
Also, Sometimes they are also just off!
![Selection_091](/uploads/73ae0d9b86cc2144e776e39068b0a461/Selection_091.png)
![Selection_090](/uploads/0e1f23e0c4ae7393735460ace905b1b7/Selection_090.png)https://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/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/177BBI Preview: Add full Obs identifier2020-07-16T10:06:32ZCarl SchafferBBI Preview: Add full Obs identifierAdd observation identifier to reco previewsAdd observation identifier to reco previewsBBI Publicationhttps://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/168IVOA: Calibration Level Mismatch2019-09-02T10:04:57ZCarl SchafferIVOA: Calibration Level MismatchA standard for Data level definitions is needed. IVOA provides a definition they want to see used, however, this definition does not match up with the data Level usage commonly used at KIS.
# Our Definitions
The definitions we use curre...A standard for Data level definitions is needed. IVOA provides a definition they want to see used, however, this definition does not match up with the data Level usage commonly used at KIS.
# Our Definitions
The definitions we use currently are (to the best of my knowledge):
0. Raw Data
1. Calibrated/ Reconstructed Data
2. Scientific information such as Dopplergrams
3. Inversions
# Definitions of Calibration Levels by IVOA
![Selection_063](/uploads/018dace8f7cf2365b5eb08aa8b6b6b10/Selection_063.png)
# Solarnet on Data Levels
>The concept of "data level" is often used to label data with a particular degree of processing,
from raw data up to complex data products.
However, definitions of data levels are extremely instrument-/mission-/pipeline-dependent, and
not very useful in terms of explaining what processing has been applied. This concept is useful,
however, to ensure that files with different processing level have unique file names. For this
reason, the keyword
LEVEL
may be used, as a string value to capture sub-levels such as quick-
look versions.
# Examples
![Selection_062](/uploads/58d1b2d7076f50afba80a7daf0d7d8d4/Selection_062.png)https://gitlab.leibniz-kis.de/sdc/kis_tools/-/issues/162bbi: add docstrings2020-07-16T10:08:01ZCarl Schafferbbi: add docstringsBBI Publicationhttps://gitlab.leibniz-kis.de/sdc/issue_collection/-/issues/1lars coordinates2020-07-16T09:58:23ZCarl Schafferlars coordinatesLars coordinates are messed up somehow. The keywords specifying the location on the disk exhibit problems:
Coordinates are given via two redundant sets of keywords:
1. `SHG_LAT` and `SHG_LON` give the [Stonyhurst Heliographic Coordinates...Lars coordinates are messed up somehow. The keywords specifying the location on the disk exhibit problems:
Coordinates are given via two redundant sets of keywords:
1. `SHG_LAT` and `SHG_LON` give the [Stonyhurst Heliographic Coordinates](http://www.mssl.ucl.ac.uk/grid/iau/extra/local_copy/coordinates.pdf) position in degrees according to the header
2. `HPC_X` and `HPC_Y` give heliographic coordinates in arcsec
If these coordinate information sets match up, there should be a steady relationship between them. Plotting reveals some sort of mismatch:
![Selection_053](/uploads/3470b353f6c289d7b67091858fb6fee7/Selection_053.png)https://gitlab.leibniz-kis.de/sdc/kis_tools/-/issues/85tagger add description of map2020-07-16T10:24:46ZCarl Schaffertagger add description of mapmap length (pixel size in particular)map length (pixel size in particular)