-
Notifications
You must be signed in to change notification settings - Fork 6
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
Rethink assays nomenclature #194
Comments
Following @cvanderaa 😀 as you know we use CCing @Charl-Hutchings @csdaw |
Could you share your thoughts on this. In our latest paper, we refer to the elements of a QFeatures object as sets. (@samgregoire, could you confirm). |
I confirm.
|
This great 👍 I think |
my vote for "experiments" based on discussions on #197 |
As discussed for the protocol paper with @samgregoire, the fact that the quantitative data in a
SummarizedExperiment
and the data objects in aQFeatures
are both calledassays
complicates the description of the data structure.I would suggest renaming the
QFeatures
'assays
.sets
: it is generic, like data sets (and in honor of the previously supportedExpressionSet
class)experiments
: because each object is a[SingleCell|Summarized]Experiment
. Actually, the objects inQFeatures
are retrieved usingexperiments(qf)
.elements
: because each object is in fact an element of a list (ExperimentList
)The text was updated successfully, but these errors were encountered: