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

Per-Analysis Developer Stats #32

Closed
cellistigs opened this issue Dec 15, 2020 · 5 comments
Closed

Per-Analysis Developer Stats #32

cellistigs opened this issue Dec 15, 2020 · 5 comments

Comments

@cellistigs
Copy link
Collaborator

Create a module in neurocaas_contrib to read in a blueprint that you own. From this blueprint, retrieve statistics on:

  • Active users
  • Per-user usage
  • Analysis version being used
  • Job success or failure per dataset.

Collect these statistics, and aggregate them across all analyses to add usage quantifications to the paper.

@cellistigs
Copy link
Collaborator Author

The completion of this will also close #11.

@cellistigs
Copy link
Collaborator Author

Incorporate code that you wrote for CZI analysis statistics:
Get use activity across a variety of different buckets:

  • dev_utils/process_usage.py
  • dev_utils/track_usage.py

Output file:

  • dev_utils/neurocaas_activity.json

@cellistigs
Copy link
Collaborator Author

Add in code to get lambda monitoring info (usually printed to cloudwatch logs), the number of instances currently running, and information from ssm about your current job.

@cellistigs cellistigs moved this from To do to In progress in NeuroCAAS Developer Workflow/Paper Edits Feb 3, 2021
@cellistigs
Copy link
Collaborator Author

Per analysis stats can now be read in, with a view towards the amount of parallelism used.

@cellistigs
Copy link
Collaborator Author

Integrated with cli. Analysis version is given by certificate, so we're good here.

NeuroCAAS Developer Workflow/Paper Edits automation moved this from In progress to Done May 14, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Development

No branches or pull requests

1 participant