search

jbrzusto / TO_DO

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

Registered receiver data going to project 0 #103

Open zcrysler opened 7 years ago

zcrysler commented 7 years ago

Data from Binbrook SG-0816BBBK009E is going to https://sensorgnome.org/download/0 despite it being registered to project 1 - Motus receiver deployment 2136

Lotek-345 (motus receiver ID 2161) in project 31 is going to project 0 despite it being registered and activated

zcrysler commented 7 years ago

Same with receiver SG-3F8CRPI32CF2 for project 48, job ID 576191

zcrysler commented 7 years ago

And receiver SG-6581RPI35065 for project 48, job ID 665182

jbrzusto commented 6 years ago
serno details
SG-0816BBBK009E the only deployment record returned by the API ends Mon Jul 10 12:31:00 GMT 2017; data from batches not overlapping that deployment have to go somewhere, so they go to project 0. If a deployment is still operational, it shouldn't have an end date in the past.
Lotek-345 the only data file was processed July 19. I think the deployment record was added after that.
SG-3F8CRPI32CF2 job 576191 was processed Aug. 30, at which time there was no deployment record for this recv; subsequent uploads have sent their products to https://sensorgnome.org/www/48 as they should.
SG-6581RPI35065 no deployment record returned by API.

Once a product file is generated, it doesn't get moved around on the server, even if subsequent deployment records change. These products are just supposed to be provisional anyway. The "real" data, that reflects changes in deployment info, is obtained via the motusClient package.