eSASS Q&A / weekly eSASS developers Zoom meeting
Start of meeting: 2020-05-05 13:30 (1:30pm) - Zoom link: https://zoom.us/j/7909307159?pwd=ZEdGeTJQUzdsRGpkd2Q5aUZXQmZZdz09
The weekly eSASS developers meeting on the first Tuesday of each month is announced to the full eROcat list to facilitate interaction between eSASS users and developers (eSASS Q&A). Question, bug reports, and suggestions for improvements are welcome.
Agenda:
eSASS Q&A
In the previous eSASS Q&A meeting Jeremy Sanders presented the eROSITA Sky Explorer eROSE. A video of his presentation is available here. Those who tried out eROSE in the last month are welcome to provide feedback.
- Other eSASS questions, bug reports, suggestions, etc.
- CalPV data should have source catalogs!
- Backdating current boresight caldb files to also apply to CalPC data.
- evtool, srctool TSTART and TSTOP header keywords (other?) should match GTI
- from last (ad-hoc) background meeting (24-Apr): missing S/W package like "esas" and "eimageget"/"eimagecombine" in XMMSAS, would be very helpful and could be a joint eRO_DE effort
- Weekly eSASS developers team meeting
- Preprocessor / NRTA
- Data analysis pipeline
- c946 processing - where are we?
- evprep/evatt new time correction method / testing
- uncorrected event lists: evatt warning?
- evatt in new users release will not work with c945 data! evatt warning and documentation!
- uncorrected event lists: evatt warning?
- new vignetting model
- new 2dpsf and avignet2 caldb files / srctool-1.52 (expmap needs to be rebuilt)
- avignet/avignet2 file names are in expmap/srctool SASSHIST keyword
- evprep/evatt new time correction method / testing
- New eSASSusers release
- New TM5/TM7 flickering pixels/corrupted events?
- put bad pixel TSTART, TSTOP values into badpix caldb files
- check corrupted event/frame algorithm in evprep
- Pipeline reruns (fields with large exposure gradient, test scan fields)
- BARYCORR (Joern's code)
- DATool
- Pipeline data quality checking (GTI fraction, corrupted events, etc.)
- c946 processing - where are we?