Skip to content
GitLab
    • GitLab: the DevOps platform
    • Explore GitLab
    • Install GitLab
    • How GitLab compares
    • Get started
    • GitLab docs
    • GitLab Learn
  • Pricing
  • Talk to an expert
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
    • Switch to GitLab Next
    Projects Groups Topics Snippets
  • Register
  • Sign in
  • satnogs-network satnogs-network
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributor statistics
    • Graph
    • Compare revisions
    • Locked files
  • Issues 195
    • Issues 195
    • List
    • Boards
    • Service Desk
    • Milestones
    • Iterations
    • Requirements
  • Merge requests 13
    • Merge requests 13
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Artifacts
    • Schedules
    • Test cases
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages and registries
    • Packages and registries
    • Container Registry
    • Model experiments
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Code review
    • Insights
    • Issue
    • Repository
  • External wiki
    • External wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • librespacefoundationlibrespacefoundation
  • SatNOGSSatNOGS
  • satnogs-networksatnogs-network
  • Issues
  • #563
Closed
Open
Issue created Dec 06, 2018 by Fabian P. Schmidt@kerel-fsDeveloper

Feature RQ: Add custom observation options/tags

It would be nice to be able to customize the behavior of the satnogs-client during an observation for specific observations. This could be implemented by custom tags, entered by the user via network when creating an observation and passed to the client.

Possible tags:

  • activate IQ data storage & upload
  • activate audio upload (in case we disable audio upload for some decoders by default in the future)
  • Choose a development-version of a gnuradio flowgraph (Fixes #378)
  • overwrite gr-satnogs script arguments, e.g.
    • frequency
    • ppm correction

All the ideas above are related to the debugging of a station or developing satnogs-client/gr-satnogs. The tags would be handed over to the client in a format transparent to satnogs-network, (as in: satnogs-network doesn't know the meaning of the tags), and the client modifies its config accordingly during the observation (non-persistent).

This feature request was extracted from a misplaced comment in #474.

To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
Time tracking