jbrzusto
commented
5 years ago I'm adding these paramOverride records:
sqlite> select t1.projectID as projectID, 'find_tags_motus' as progName, 'default_freq' as paramName, 'project listening frequency inferred from tag registrations' as why, t2.nomFreq as paramVal, datetime(min(t1.tsStart), "unixepoch") as tsStart, datetime(max(t1.tsEnd), "unixepoch") as tsEnd from tagDeps as t1 join tags as t2 on t1.tagID=t2.tagID left join paramOverrides as t3 on t1.projectID=t3.projectID and ((t3.tsStart is null or t3.tsStart < t1.tsEnd) and (t3.tsEnd is null or t3.tsEnd > t1.tsStart) ) group by t1.projectID, t2.nomFreq having t2.nomFreq != 166.38 and t3.id is null and t1.projectID != 97 order by t1.projectID, t2.nomFreq, t3.id;| projectID | progName | paramName | why | paramVal | tsStart | tsEnd |
|---|---|---|---|---|---|---|
| 9 | find_tags_motus | default_freq | project listening frequency inferred from tag registrations | 166.3 | 2013-08-05 16:44:00 | 2013-09-30 00:00:00 |
| 13 | find_tags_motus | default_freq | project listening frequency inferred from tag registrations | 166.3 | 2012-08-01 12:00:00 | 2013-10-03 16:49:15 |
| 28 | find_tags_motus | default_freq | project listening frequency inferred from tag registrations | 166.3 | 2013-07-11 18:00:00 | 2013-12-30 00:00:00 |
| 36 | find_tags_motus | default_freq | project listening frequency inferred from tag registrations | 166.3 | 2016-09-08 12:00:00 | 2016-11-30 21:48:16 |
| 41 | find_tags_motus | default_freq | project listening frequency inferred from tag registrations | 150.1 | 2016-04-01 00:00:00 | 2016-12-01 03:52:06 |
| 41 | find_tags_motus | default_freq | project listening frequency inferred from tag registrations | 160.4 | 2016-07-01 00:00:00 | 2016-09-29 00:00:00 |
| 62 | find_tags_motus | default_freq | project listening frequency inferred from tag registrations | 166.32 | 2018-04-01 00:00:00 | 2018-08-10 12:22:40 |
| 62 | find_tags_motus | default_freq | project listening frequency inferred from tag registrations | 166.36 | 2018-04-01 00:00:00 | 2018-08-10 12:22:54 |
| 76 | find_tags_motus | default_freq | project listening frequency inferred from tag registrations | 150.44 | 2015-01-01 00:00:00 | 2015-04-27 19:53:11 |
| 85 | find_tags_motus | default_freq | project listening frequency inferred from tag registrations | 160.38 | 2016-12-23 00:00:00 | 2017-06-29 15:22:59 |
| 108 | find_tags_motus | default_freq | project listening frequency inferred from tag registrations | 166.3 | 2016-01-01 00:00:00 | 2016-07-01 15:37:36 |
| 121 | find_tags_motus | default_freq | project listening frequency inferred from tag registrations | 150.1 | 2017-09-23 00:00:00 | 2017-11-21 01:34:58 |
| 170 | find_tags_motus | default_freq | project listening frequency inferred from tag registrations | 151.5 | 2017-09-03 09:30:00 | 2017-11-10 07:14:41 |
| 173 | find_tags_motus | default_freq | project listening frequency inferred from tag registrations | 150.1 | 2017-10-12 08:27:00 | 2018-07-05 03:20:50 |
| 182 | find_tags_motus | default_freq | project listening frequency inferred from tag registrations | 150.1 | 2018-06-06 00:00:00 | 2018-07-29 18:31:08 |
| 186 | find_tags_motus | default_freq | project listening frequency inferred from tag registrations | 150.1 | 2017-07-01 00:00:00 | 2018-06-30 23:25:15 |
| 211 | find_tags_motus | default_freq | project listening frequency inferred from tag registrations | 150.1 | 2018-08-01 00:00:00 | 2018-12-13 18:23:03 |
The tag finder needs to know what frequency a receiver is listening at in order to select the set of tags it should be looking for. This normally happens by parsing the frequency-setting parameters in the raw data files, but sometimes those records are absent, typically because users haven't uploaded files dated "2000", which are recorded before the GPS sets the system clock. In this case, the tag finder uses the default frequency specified as the command-line parameter
default_freq, which itself defaults to the Western Hemisphere default of 166.376. Many projects use a different default, and these are provided as parameter overrides in theparamOverridestable in the database/sgm_local/motus_meta_db.sqlite. These overrides can be specified by project or by receiver and by time period.To be fixed:
ruleID(i.e. projects for which there are tags registered to nominal frequencies other than 166.38 but for which there is no project-specific parameter override):paramOverridesrecord matching that frequency and covering the tag's deployment period, on the assumption that receivers for a project are listening for tags from that project. This should come with a warning that if there are unusual circumstances (e.g. a project with receivers listening to different frequencies from each other), they need to haveparamOverridesrecords added manually.