https://github.com/atrisovic/caliper

Caliper is a tool for measuring and assessing change in packages.

https://github.com/atrisovic/caliper

Science Score: 10.0%

This score indicates how likely this project is to be science-related based on various indicators:

  • CITATION.cff file
  • codemeta.json file
  • .zenodo.json file
  • DOI references
  • Academic publication links
    Links to: zenodo.org
  • Academic email domains
  • Institutional organization owner
  • JOSS paper metadata
  • Scientific vocabulary similarity
    Low similarity (12.7%) to scientific vocabulary
Last synced: 10 months ago · JSON representation

Repository

Caliper is a tool for measuring and assessing change in packages.

Basic Info
Statistics
  • Stars: 0
  • Watchers: 1
  • Forks: 0
  • Open Issues: 0
  • Releases: 0
Fork of vsoch/caliper
Created over 5 years ago · Last pushed over 5 years ago

https://github.com/atrisovic/caliper/blob/main/

![docs/assets/img/caliper-logo-sketch.png](docs/assets/img/caliper-logo-sketch.png)

[![PyPI version](https://badge.fury.io/py/caliper.svg)](https://badge.fury.io/py/caliper)
[![Documentation Status](https://readthedocs.org/projects/caliper-python/badge/?version=latest)](https://caliper-python.readthedocs.io/en/latest/?badge=latest)
[![DOI](https://zenodo.org/badge/322702177.svg)](https://zenodo.org/badge/latestdoi/322702177)

Caliper is a tool for measuring and assessing change in packages.

![docs/assets/img/spack-changes.png](docs/assets/img/spack-changes.png)

See the [documentation](https://caliper-python.readthedocs.io/en/latest/) for getting started.

## TODO

- write tests to discover and test all metrics (type, name, etc.)
- think of common functions to run metric
- create visualization of grid of errors / scripts, and mouesover to see codes (server rendered)
- stats: try to estimate types of codes (e.g., error name)

### Analysis Ideas

1. Start with a bunch of unit tests for a library (or example scripts) and build a model that can predict success (return code 0) vs fail (any other code) based on the scripts (tokens is a simple idea). Then given a new script without declared versions, predict which will work.
2. (A slightly different project) - given a set of known "optimal" containers for a library like tensorflow, parse dependencies, versions, and library versions, run across same set of unit tests / example scripts, and try to say which combos (architecture and dependencies) works for different kinds of scripts.

## License

 * Free software: MPL 2.0 License

Owner

  • Name: Ana Trisovic
  • Login: atrisovic
  • Kind: user
  • Location: Cambridge, USA
  • Company: Harvard University

Computer Scientist and #Reproducibility Researcher at @HarvardBiostats & @IQSS | previously with @UChicago, @Cambridge_Uni and @LHCbExperiment @CERN

GitHub Events

Total
Last Year