Authors: Ian Pendleton, Michael Tynes, Aaron Dharna
Science Contact: jschrier .at. fordham.edu, ian .at. pendletonian.com
Technical Debugging: vshekar .at. haverford.edu, gcattabrig .at. haverford.edu,
Alternative Debugging: mtynes .at. fordham.edu, adharna .at. fordham.edu
A detailed description of the current functionality and logic for this code can be in the original ESCALATE publication.
User documents can be found here.
This code has been tested on MacOS High Sierra and Ubuntu 18.04 LTS. Though written in python the code interfaces with Google API and may require debugging for operation on other operating systems and IDEs.
To build the proper environment using anaconda (https://conda.io/docs/user-guide/install/index.html) do the following:
-
Deactivate any current conda instance:
conda deactivate
-
Create new python 3.7 environment in conda
conda create -n escalate python=3.7
-
Activate the new environment
conda activate escalate
-
Execute the following additional command:
pip install -r requirements.txt
-
If you need to run the mathematica sampler please install wolfram engine on your operating system. Follow instructions here: https://www.wolfram.com/engine/
- Once installed please change the sampler option from 'default' to 'wolfram' in the file capture/devconfig.py
- Wolfram occasionally updates the engine. Default is set to detect version 12.1. If you receive a 'wolfram client' not found error, please check the linux_path in ./capture/devconfig.py
If during the installation process you encounter any issues, please submit a bug report / issue to https://github.com/darkreactions/ESCALATE_Capture
Installation on Windows:
-
Download and unzip the zip file (or use git clone) of the ESCALATE capture code
-
Download and install wolfram engine --> and be sure to activate!!!
- Wolfram occasionally updates the engine. Default is set to detect version 12.1. If you receive a 'wolfram client' not found error, please check the linux_path in ./capture/devconfig.py
-
Open a miniconda window and navigate to the unzipped ESCALATE_Capture-master folder
-
Create new python 3.8 environment in conda. (This can also be installed in the same environment as the ESCALATE_report)
conda create -n escalate python=3.8
-
Activate the new environment
conda activate escalate
-
Install necessary python packages using pip
pip install -r requirements.txt
-
If they have already been created, you will need to request the securekey [json] files from your support team and move them into the root folder (
./
, aka. current working directory, aka.ESCALATE_Capture-master/
if downloaded from git). Do not distribute these keys! (Contact a dev for access, or setup your own)Note: If your in a hurry, Ian says you can try getting the securekey files here: securekey files
-
Ensure that the files 'client_secrets.json' and 'creds.json' are both present in the root folder (
./
, aka. current working directory, aka.ESCALATE_Capture-master/
if downloaded from git). The correct folder for these keys is the one which contains the runme.py script.
Detail User Instructions can be found here.
-
Ensure that your computer local time is updated and accurate. If necessary look up how to syncronize your system with internet time.
- This ensures that the runs have the correct creation information
-
Open the variable container XLSX file of your choice (ex. MIT_SpecificationInterface.xlsx)
-
Update the variables in the XLSX (see this example for more deatailed instructions)
-
Please ensure that the conditions fall within the indicated ranges and are compatible with the workflow (see ex. solubility data tabs )
- If the run fails, see the FAQs!
-
Follow additional guidelines for each variable as outlined in .xlsx interface.
-
Execute the script by running
python runme.py <my_specification_file>.xlsx
ex.
python runme.py MIT_SpecificationInterface.xlsx
-
Script will generate files in the "1-Dev" folder of the shared google drive
- Ensure that desired run information has been generated correctly
- Move the validated directory to the 2-ExpDev directory (examples here)
- Note: The Dev folder should be periodically cleared to ensure that the latest runs can be easily located
- Code for postprocessing can be accessed here: https://github.com/darkreactions/ESCALATE_report