Investigating the two regimes of fibrin clot lysis: an experimental and computational approach

Open data API in a single place

Provided by Zenodo

Get early access to Investigating the two regimes of fibrin clot lysis: an experimental and computational approach API!

Let us know and we will figure it out for you.

Dataset information

Country of origin
Updated
2021.08.18 00:00
Created
2021.01.01
Available languages
English
Keywords
Quality scoring

Dataset description

  Investigating the two regimes of fibrin clot lysis: an experimental and computational approach Dataset and python files (Python3) to reproduce all figures and simulations presented in the manuscript.   ********************** * Run_simulations.py * ********************** * To run the simulations:   python3.8 Run_simulations.py arg1 arg2 arg3 arg4   - arg1:     Directory with experimental lysis profiles      - arg2:     Directory to store initial conditions of the lysis (i.e state of the system after clot formation)     if the directory does not exist, it is created.      - arg3:     Directory to store the simulated lysis profiles     if the directory does not exist, it is created.    - arg4:      index of the first set of clotting kinetic parameters (92 sets of parameters)    - arg5:      index of the last set of clotting kinetic parameters (92 sets of parameters) * Example: python3.8 Run_simulations.py Raw_Data/ Init/ Results/ 0 92 * Requires:   - module_fibrin_polymerization_Diamond_kinetics.py   - module_kinetics.py   - solid_Diamond_Anand_dict.py (dictionnary with parameters of the simulations)   - output_parameters_polymerization_T1000.txt (sets of clotting kinetic parameters)   - Mean_LAT_LYS_shell.txt (mean fraction of shells during slow and fast lysis for each experiment. Used to compute the distribution of shells for the surrogate model) **************************************** * make_analysis_figures_simulations.py * **************************************** * To reproduce the figures associated to simulation results:   python3.8 make_analysis_figures_simulations.py arg1 arg2 arg3 arg4   - arg1:   Directory with experimental lysis profiles   - arg2:   Directory with the simulated lysis profiles   - arg3:   Directory with initial conditions   - arg4:   Directory with the results of the sensitivity analysis * Example: python3.8 make_analysis_figures_simulations.py Raw_Data/ Results/ Init/ Sensitivity_Analysis/ * PDF Figures are created in the current directory * Requires:   - module_analyze_simulations.py   - module_analyze_data.py   - output_parameters_polymerization_T1000.txt   - manip_summary.txt (clot formation time, slow lysis time, fast lysis time for each experiment)   - Experiments_sorted.txt (experimental conditions, sorted by increasing order of concentrations) **************************************** * make_analysis_figures_experiments.py * **************************************** * To reproduce the figures associated to experimental results:   python3.8 make_analysis_figures_experiments.py arg1   - arg1:   Directory with experimental lysis profiles * Example: python3.8 make_analysis_figures_experiments.py Raw_Data/ * PDF Figures are created in the current directory * Requires:   - module_analyze_data.py   - Experiments.txt (contains experimental conditions)  
European data infrastructure with broad catalog discovery, free evaluation access and production-grade API options.
190K+
indexed dataset pages
32
countries and EU institutions
2019
API-first since
Free API quota
for evaluation and prototypes
SLA
history and push on production APIs
FAQ

Questions before production use

Practical answers on evaluation, licensing, freshness, versioning and support.

api.store is built and operated by Apitalks s.r.o. Company details and a direct contact path are linked in the footer for vendor checks and procurement review.
Yes. Selected APIs include a free API quota, so your team can validate coverage, freshness, response shape and workflow fit before asking for a production plan.
Often yes, but usage rights depend on the source license and dataset. We surface source, license and update metadata where available, and can help review terms before a production integration.
Maintained APIs include update metadata where available. For production integrations, we can add history, monitoring and push updates so changes are easier to detect and act on.
Production APIs can add SLA, stable identifiers, versioning support, history, push updates and direct support around the data your product or AI workflow depends on.

Didn't find the API you need?

Let us know and we will figure it out for you.

European data discovery with free evaluation access and production-grade API options.

Copyright © 2026. Made by Apitalks