Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add Data Acquisition (DAQ) classifier #184

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

stephanlachnit
Copy link

Adds a classifiers for software packages that provide or work with DAQ systems (https://en.wikipedia.org/wiki/Data_acquisition).

Request to add a new Trove classifier.

The name of the classifier(s) you would like to add:

  • Topic :: Scientific/Engineering :: Data Acquisition (DAQ)

Why do you want to add this classifier?

Data acquisition (DAQ) systems are common place to read data from sensors or other data sources. While typically a lot of DAQ software is written in low-level programming languages, writing DAQ software in Python is getting more common. A simple search for keywords like "data acquisition", "sensor", "readout" and "daq" and reveal many packages that could use such a classifier.

The current classifiers are not sufficient: searching for "data" only reveals three database and a framework entry, "hardware" doesn't include any readout classifiers and in scientific/engineering are many DAQ-related classifiers (like "physics", "information analysis"), but none that actually provide a clear indication for hardware/DAQ-related packages.

Adds a classifiers for software packages that provide or work with DAQ systems (https://en.wikipedia.org/wiki/Data_acquisition).
@di
Copy link
Member

di commented Jul 5, 2024

Hi! Thanks for the request. The PyPI moderators are in the process of developing a few guidelines for the creation of new Framework classifiers. Because removing classifiers is very difficult, and the longer the classifier list gets the harder it is to browse, I think we're expecting the bar to add new ones to be relatively high. Currently, we're looking at these guidelines:

  • New Framework classifiers should be created if they are "notable;" and
  • They will be of immediate use to existing projects (in other words, no creating classifiers simply in anticipation of future uses)

We understand that "notability" is subjective and we'd appreciate help judging that.

As to the other guideline ('immediate use to existing projects'), it's been suggested that

  • Requestors can demonstrate this by providing links to 10 or more existing PyPI projects that have expressed a desire to use the classifier; or
  • Another way to demonstrate this would be to have 10 or more other project maintainers submit comments on the requesting issue about their desire to use the classifier.

Thanks!

@stephanlachnit
Copy link
Author

Hi @di,

thanks for the reply and I totally understand. I can speak for Constellation, we would definitely use that classifier. I will ask around to see if other projects would join this effort.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants