Please add support for CzechRad CZRA1 header code

[juhele]

safecastapi/app/models/bgeigie_import.rb

Line 179 in 6cf3612

return false unless [

First prototype units used CZRDD, current CzechRads use CZRA1, in future possibly others like CZRA2, CZRB1 - this is because in case of commercial production of CzechRads there might be device number assignment conflicts if we had only CZRDD code.

thanks

References:
https://github.com/juhele/CzechRad/tree/main/DATA

[robouden]

Jan,

To make the change in the code would be easy. But to get it deployed and in the app, we do not currently have anyone who is confident in doing that and who can allocate time for doing that. I would suggest making a change to use the old header till we can add your new header to the log file.

Regards
Rob

[juhele]

oops,
I think we will have to wait because we already have several hundreds of CzechRads in the field and there is no way to do such change remotely...

the only way would be to change it in every LOG file... (probably possible with some batch script) but reuploading those 700 LOGs looks like a nightmare...

[robouden]

Yes, we notice about 750 (according to Pieter). It would have been helpful if you had tested one upload only and see if that worked. BTW.. For the changing of the header in the batch file, you have to recalculate the chksum too.

Regards
Rob

[juhele]

I had the same issue at the beginning with the prototype data with old header so I thought you did not yet implemented it. Later, during uploading I noticed that old data is imported correctly but new not...

The checksum is not problem if I load and save the LOG from QGIS. However, both data types are displayed correctly in the API.
In addition the Tilemap is still not being updated yet so we have to wait anyway...

[robouden]

Jan, For getting drives approved, you need a correct checksum. I tried with a file you had uploaded and only changed the header string. It did upload but could not be processed/approved due to checksum errors. Regards Rob

…

On Thu, Sep 12, 2024 at 11:15 PM Jan Helebrant ***@***.***> wrote: I had the same issue at the beginning with the prototype data with old header so I thought you did not yet implemented it. Later, during uploading I noticed that old data is imported correctly but new not... The checksum is not problem if I load and save the LOG from QGIS. However, both data types are displayed correctly in the API. In addition the Tilemap is still not being updated yet so we have to wait anyway... — Reply to this email directly, view it on GitHub <#1034 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAKSVNTO7KI3PQ3XLIR5V7TZWGOZJAVCNFSM6AAAAABODDZRL6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDGNBWGQZDMMBRHA> . You are receiving this because you commented.Message ID: ***@***.***>

[juhele]

RadiationToolbox handles the checksum when saving the LOG file. So you recommend to manually change the newly uploaded CzechRad LOGs to "legacy" header CZRDD to temporarily solve this issue? (until properly implemented) PS: I don't think it's within my time to redo the previously uploaded files as new measurements keep pouring in... And I think it it quite important to manage the quality control.

[robouden]

Jan,

I will try one file and report back to you if that setup works. Please wait.

Regards
Rob

[robouden]

Jan,

Just tested it and your idea works, see: https://api.safecast.org/en-US/bgeigie_imports/64632
Hugs and peace,
Rob

[robouden]

Jan,

I think you can also script a batch that can upload directly (from https://api.safecast.org):

[juhele]

OK,
a temporary solution consisting of manual conversion to legacy CzechRad code seems to work:
https://api.safecast.org/en-US/bgeigie_imports?by_user_id=6776&order=created_at+desc
I will use it for new data files, but I hope that after implementation into the API it will be possible to load (previously uploaded) files with the new CzechRad code in the future...

[robouden]

Jan,

Thanks for using the temporal solution.
I also hope we can fix the issue soon.

Regards
Rob