Seven attributes have under 35 annotations; merge or leave out of the release

Abierto
#268 0 comentarios 0 reacciones 0 asignados Ver en GitHub

Los mantenedores suelen responder en 1 día

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
4/5
Tiempo estimado
1-2 días
Aptitud para principiantes
22/100
Tipo de issue
Refactorización
Claridad
Bastante claro
Estado de actividad
Activo
Stack tecnológico
r
Área
data

Línea de trabajo

The payload names no files, tests or entry points, only the attribute names and their annotation counts. Start by finding where those attributes are defined in the annotation sheets, and confirm the counts. The issue asks the maintainer to choose between merging the producing traits into one metabolic product attribute and holding back the under-100 attributes from the release, so a newcomer should not start until that decision is made.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

curation

Ten of the 32 attributes have fewer than 100 source annotations, six fewer than 30: health associated (29), butyrate-producing bacteria (28), mutation rate per site per year (33), mutation rate per site per generation (26), sphingolipid producing (20), lactate producing (15), hydrogen gas producing (14). None of them can be propagated by ASR or make a signature of the default minSize = 10 at most ranks. Counting them as attributes in the paper ("32 attributes") overstates the resource.

Options, pick one:

  1. Fold the "producing" traits into a single multistate-union attribute metabolic product (acetate, butyrate, lactate, hydrogen gas, sphingolipid) and add sources: Madin 2020 and BacDive both have fermentation products, and #144 asked for this in 2022.
  2. Keep them in the sheets but leave them out of the release and the manuscript count until each has, say, 100 annotations.

I'd do both: merge, then apply the floor.

Drafted with Claude Code.

Lenguaje dominante
R
Estrellas
6
Forks
6
Merge medio
1 h 48 min
PR fusionados (30 d)
13

Preparar el entorno

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de waldronlab/bugphyzz

Todos los issues de waldronlab/bugphyzz

Issues similares

Más issues de R

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.