Skip to content

Conversation

@jankrepl
Copy link
Contributor

@jankrepl jankrepl commented Oct 8, 2025

Closes #355

TODO

  • Integrate morphology metrics (the lazy way)
  • Integrate morphology metrics the proper way
  • No need to pass an argument list[str] that decides on what features will be extracted. Instead, each of the output fields is a separate resolver.
  • Also, it would be convenient for the metrics that spit out a list[float] to have some wrapper that also provides lenght, mean, std, values so that one does not always have to fetch all of them.
  • And now it makes me think maybe you could understand how the pagination across the values would work.
  • Support both single morphologies and bulk morphologies
  • Integrate circuit metrics
    • Imply level of detail based on the query
    • Issue below
    TypeError: CircuitMetricsNodePopulationType fields cannot be resolved. Unexpected type 'dict[str, list[str]]'
    
  • Fix CI

Comments

  • I originally wanted to do it for ephys metrics but they I realized that the output type is basically just dict[str, Any] which is useless for GraphQL. I therefore decided to switch to morphometrics

@jankrepl jankrepl changed the title (POC) - GraphQL ephys metrics (POC) - GraphQL morpho metrics Oct 9, 2025
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.

(POC) Using GraphQL for declared metric endpoints

2 participants