New stations not automatically added to 'Detector HiSPARC' about publicdb

[davidfokkema]

It should, indeed. It used to be the case that a default, empty, DetectorHisparc object would be created when the station was created in inforecords. The /usr/local/hisparc-update script running daily on pique (source in examples/django-cron.py in the publicdb tree) updates all DetectorHisparc objects with the latest GPS positions. However, that object needs to exist.

[153957]

So the question is why were those DetectorHisparc objects not created, I noted that some other stations also do not have a corresponding DetectorHisparc object.
For now we can manually create them for those stations which do not have it, since it won't be generated automatically because the stations already exists.

[153957]

This is the reason that jsparc would not work when trying to retrieve data for newer stations, they did not have an entry in DetectorHisparc, causing the retieval of the gps information to fail in django_publicdb/jsparc/views.py at
d = s.detectorhisparc_set.all().reverse()[0]. Causing an IndexError which is not caught.

[davidfokkema]

I've checked the code. The DetectorHisparc object is never created, nor referenced. The wizards would've taken care of that. I suggest that for now, the objects need indeed manually be created when a station is created. Later, a rewrite of inforecords should take care of this.