Skip to content

TODOs

Jump to bottom Edit New page
Christopher Patton edited this page Sep 27, 2013 · 10 revisions

High-level

  1. Structure of DB schema for det, est, higher order data types, as well as queries for the various calculations.
  2. Calibration - test data collection (in progress) and calculations. Todd
  3. Direction finding. Todd
  4. False-positive discrimination. Marcel
  5. Bearing/position estimation to improve false-positive discrimination.
  6. position estimation to improve calibration and bearing.
  7. Processing of modulated telemetry transmitters. Test transmitter GPS AFSK reception and de-modulation and a build a generic tool for df and de-modulation. Todd
  8. Transmitter listening schedule. Create an interface for users to input which tags they want to track, where they are supposed to be (node locations), and what time they should be listening. A schedule for each node. is then calculated and updated. Todd outlined this idea here. Chris? This would be fun.
  9. Automated RF status: check each channel is functioning, automated detector parameter optimization (e.g precalculate noise floor). Eliminate fall_factor. Todd

Data output

  1. Structure of higher order data types, e.g. bearing by time per site per tag, position by time.
  2. Power (signal?) by time plot per node.
  3. Current location plot per tag.
  4. Transmitter tracks over time interval map.
  5. import/export hooks for R.
  6. Frequency of production? hourly, daily, realtime?

Data flow

  1. DONE Fix automatic backup to external drive.
  2. DONE Automatically remove data from /rmg_server as to maintain enough free space.
  3. Rethink the best way to do this, hopefully when the new server is ready.
  4. FIXME in serv/rmg_csv. Standardize the way we handle and disseminate config files, include in API. Chris
  5. Clean up metadata logging and dissemination (rmg-node check stuff Todd and I talked about). Chris

System control

  1. Add machine readable "status" script to get remote status; computer ping, powerswitch ping, rmg-node status, voltage, temperature, powerswitch relay status, etc.
  2. Update control and telemetry scripts to use new "status" script, including a human readable rmg status.
  3. DONE Update PERL telemetry scripts to use rmg_csv and other utilities.
  4. Add voltage and temperature check in rmg_schedule

Documentation

  1. Structure and description of est files and det --> est.
  2. How do we use ssh?

Infrastructure

  1. Power upgrade at 20, install more panels on rack at 39.
  2. Safe shutdown of node when pingbrother voltage drops below threshold.
  3. Better passive thermal control of node sites? Active thermal control?
  4. Clean up wires in the boxes, wrap bare copper with electrical tape.

Miscellaneous

  1. Transmitter config dissemination, should restart pulse detectors. Also, schedule nodes to look at subsets of transmitters at different times. (Related to the high-level #8.)
  2. A qraat application programming interface. Chris
  3. DONE Code documentation. Chris
  4. DONEEliminate obsolete code in qraat.rmg. Move hard-coded params in python/rmg_param.py to rmg_env. Remove rmg_setup.py and dependencies.
  5. Separate web stuff from main repo.
  6. DONE Clean up naming conventions.
  7. Add error check for constructor values to peak_detector.
  8. In pulse detector, what is the purpose of status.txt and can we get rid of it? If not, add preprocessor directive for compiling outputing to status.txt.
  9. Clean up error handling in pulse detector. Catch SIGTERM in rmg_run.py to flush buffers before exit.
  10. Determine if center_frequency information in .est file is enough to separate tags which are received on multiple tunings, for activity/received power analysis
  11. Save calculated sample power in detector so psd doesn’t have to recalculate? Increase size of accumulator buffer?
  12. Increase save_holder size to eliminate peak_holder copy in detect?
  13. Make sure apps/4channel_spectrum_{serv,client} are up to date.
Add a custom footer
Add a custom sidebar

Clone this wiki locally