search

jbrzusto / TO_DO

sensorgnome / motus TODO list for jbrzusto
0 stars 0 forks source link

Duplicate receivers #176

Open zcrysler opened 6 years ago

zcrysler commented 6 years ago

These are the known duplicate receivers: SG-0517BBBK1111, Bookton/Seaview from projects 1/47 respectively SG-1614BBBK1911, sugarloaf/point lepreau from projects 74/2 respectively Lotek-270, HOFT/winous point, projects 32/64 respectively

I don't think an ongoing way has been figured out to deal with these, but I could be wrong. I know at least SG-1614BBBK1911 has no data for the sugarloaf receiver in project 74 in the hourly plots or available through tagme(). All the data for that receiver seems to be associated with the project 2 deployment. The user for project 74 has asked a number of times when she can get her data, is it close?

Some references, I think there are more: https://github.com/jbrzusto/TO_DO/issues/120 https://github.com/jbrzusto/TO_DO/issues/123 https://github.com/jbrzusto/motusServer/issues/297

jbrzusto commented 6 years ago

The API infrastructure is now in place to handle these, and the DB has been populated with rules for these three pairs of receivers, so that any files we receiver from them going forward will automatically get filed appropriately (see jbrzusto/motusServer#363 ). I still need to verify that for each pair, all the existing files have been assigned correctly, and then sort out and re-run any receivers where they're not.

It's possible I need to back out some file renaming in the file_repo and corresponding receiver DBs: I had initially planned to rename raw SG files to include the new suffix, but the code doesn't do that and it's not needed, and in any case breaks rsync, as I've noted in one of the related issues.

zcrysler commented 6 years ago

I think at least SG-1614BBBK1911 is missing data for project 74