- License changed from CC 4.0 to Apache 2.0
- All source files' headers replaced
- LICENSE file with Apache 2.0 default
see 0.3.1
see 0.3.1
see 0.3.1
- Only IMS and IMP product processing
- Azimuth compression windowing is yet to be done - #2
- Processing speed (Vr) and Doppler centroid changes in azimuth direction yet to be done - #2
- Packets' ISP sensing time handling might not be 100% correct
- It is observed for the reference products that it calculates new ISP sensing times based on PRI
- Therefore products by this processor differ in sensing start/stop and first/last line times (always inside the specified sensing filter)
- Best knowledge/effort basis changes has been implemented - #17 and #16
- Various metadata fields needs further work (Some were adressed during this release)
- Final results' scaling is yet to be determined, currently it is not matching exactly the reference processor
- With the current experience/knowledge there is a "best guess" implemented
- Following metadata fields implemented:
- SQ ADS missing fields (output statistics, thresholds)
- REL_ORBIT
- ABS_ORBIT
- PHASE, CYCLE
- LEVEL 0 PRODUCT
- LEAP_XYZ
- CLOCK_STEP, UTC_SBT_TIME, SAT_BINARY_TIME
CMAKE_CUDA_ARCHITECTURESis not ignored anymore when generating via cmake- SUM consists of development 101
Kajal Haria, Fabiano Costantini from Telespazio UK
Sabrina Pinori, Marco Galli from SERCO
Andrea Recchia from aresys
- Only IMS and IMP product processing
- Azimuth compression windowing is yet to be done - #2
- Processing speed (Vr) and Doppler centroid changes in azimuth direction yet to be done - #2
- Packets' ISP sensing time handling might not be 100% correct
- It is observed for the reference products that it calculates new ISP sensing times based on PRI
- Therefore products by this processor differ in sensing start/stop and first/last line times (always inside the specified sensing filter)
- Best knowledge/effort basis changes has been implemented - #17 and #16
- Various metadata fields needs further work (Some were adressed during this release)
- Final results' scaling is yet to be determined, currently it is not matching exactly the reference processor
- With the current experience/knowledge there is a "best guess" implemented
- ERS time is corrected according to PATC files - #15
- IMP mode support along with metadata enhancements - #4
- Ground detected metadata created
- azimuth spacing, chirp ADS corrected
SOFTWARE_VERin the dataset changed toasar_gpu/M.m.p
Kajal Haria, Fabiano Costantini from Telespazio UK
Sabrina Pinori, Marco Galli from SERCO
Andrea Recchia from aresys
- Only IMS product processing
- Not all the auxiliary files are utilized, currently processor configuration file (CON), instrument characterization file (INS) and external calibration data (XCA) are in use
- Azimuth compression windowing is yet to be done - #2
- Processing speed (Vr) and Doppler centroid changes in azimuth direction yet to be done - #2
- Packets' ISP sensing time handling might not be 100% correct
- It is observed for the reference products that it calculates new ISP sensing times based on PRI
- Therefore products by this processor differ in sensing start/stop and first/last line times (always inside the specified sensing filter)
- Best knowledge/effort basis changes has been implemented - #17 and #16
- ERS time is not corrected according to PATM/N/C files - #15
- Various metadata fields needs further work
- Final results' scaling is yet to be determined, currently it is not matching exactly the reference processor
- With the current experience/knowledge there is a "best guess" implemented
- See more shortcomings at https://cgi-estonia-space.github.io/asar-focus/posts/version-0-2-shortcomings/
- Range and azimuth direction edge pixels are cut from the final result, read more
- CUDA device initialization, properties and check util
- Storing results made faster with async IMS write and higher GPU utilization - see #26 and https://cgi-estonia-space.github.io/asar-focus/posts/read-and-write-optimizations/
- Complete refactor of parsing the input files, fetching measurements and processing - almost 3x of processing time gains - #29 See more detailed description - https://cgi-estonia-space.github.io/asar-focus/posts/read-and-write-optimizations/
- Better handling of missing packets and various fields for handling the missing measurements etc
- Usage of external calibration file for scaling factor guess - #34
- Final results without artifacts and 'nodata' pixels - see #33 and https://cgi-estonia-space.github.io/asar-focus/posts/range-and-azimuth-window/
- Hamming window applied for range compression - #34
- More metadata fields computed/assembled
- Invalid read of single additional sample of Envisat measurement fixed - #30
- Memory leak of the compressed sample block fixed - https://cgi-estonia-space.github.io/asar-focus/posts/read-and-write-optimizations/
- Additional output for plot (
--plot) that enables to analyze the geolocation of the scene and basic parameters - Fixed azimuth direction artifacts with padded lines for compression - see #33 and https://cgi-estonia-space.github.io/asar-focus/posts/range-and-azimuth-window/
- Envisat results scene geolocation inaccuracy fixed by applying gate bias/delay in the calculation - #33
- More modules formed as CMake targets with unit tests
Kajal Haria, Fabiano Costantini from Telespazio UK
Sabrina Pinori, Marco Galli from SERCO
Andrea Recchia from aresys
- CLI arguments are defined and shall be used correctly in order to invoke processing, no more positional arguments
- Only IMS product processing
- Not all the auxiliary files are used/supported, only instrument (INS) and configuration (CON)
- Range and azimuth compression windowing is yet to be done - #2
- Processing speed (Vr) and Doppler centroid changes in azimuth direction yet to be done - #2
- This means that the focussing quality is not exactly on par with the reference processor
- Packets' ISP sensing time handling might not be 100% correct
- It is observed for the reference products that it calculates new ISP sensing times based on PRI
- Therefore products by this processor differ in sensing start/stop and first/last line times (always inside the specified sensing filter)
- Best knowledge/effort basis changes has been implemented - #17 and #16
- ERS time is not corrected according to PATM/N/C files - #15
- Metadata for SQ_ADS, CHIRP_PARAM_ADS, etc. is not constructed currently - #10
- Other non DSD specific metadata as well - LEAP_SIGN, LEAP_ERR, ORBIT etc...
- Final results' calibration constant is yet to be determined, currently it is not matching exactly the reference processor
- With the current experience/knowledge it must be experimented and tested, no known specific formula for it
- Sensing start and end arguments
- ERS and ENVISAT missing packets insertion
- For ENVISAT all calibration packets are inserted with echo packet
- Different modes/products generation is tracked and handled accordingly
- Less explicit exits, everything is routed through exceptions with descriptive messages
- Proper log system setup using Boost log, with 5 levels. Can be set when invoking the processor
- Aux folder handling more robust - can identify aux files implicitly
- Can parse proper orbit file out of the folder with miscellaneous aux files (TDS sets)
- Echo metadata is ERS and ENVISAT specific, more fields parsed and used during processing (packet counters for example)
- Diagnostic metric by default enabled, they are printed out after parsing step (different counters out of sequence and gap metrics)
- Minor metadata improvements regarding processor, ref doc, compression method
- FEP annotations' MJD for ENVISAT is parsed correctly
- Faster parsing/preparing of echos from input dataset, from 1++ second to ~0.7 second
- Output file
FILEhandle check and other undefined states now guarded - Half of the modules are now CMake modules with unit tests
- Can be compiled with clang (version 14 tested) as well, compiler flags and build improvements executed for this
Kajal Haria, Fabiano Costantini from Telespazio UK
Sabrina Pinori, Marco Galli from SERCO
Andrea Recchia from aresys
- Added CUDA architecture support from 5.0 to 8.0 for the released binaries
- Final calibration of the foccussed pixels is not done in order to adhere to the baseline processor
- ERS and ENVISAT packets are not filtered correctly - i.e. by sensing start/end or broken ones - all of the packets are included for processing
- Minor pixel offsets/shifts are present
- No PATC/PATN information is included for ERS on board time correction
- Residue blocks are not processed for ENVISAT, only the whole 64 chunks are (range size a little smaller)
- Initial version with ERS and ENVISAT IM support with only IMS target
- Doris Orbit files are supported
- Auxiliary files support for configuration and instrument dataset
Kajal Haria, Fabiano Costantini from Telespazio UK
Sabrina Pinori, Marco Galli from SERCO
Andrea Recchia from aresys