alpha testing

[timothyfraser]

alpha testing for moves_anywhere

Next, we're going to test out a bunch of functionalities with MOVES Anywhere.
Tagging in colleagues so that you can check off any tests that you run too.
@ccloss65536 @em843 @Alirezayazdiani

Getting setup

• Ask Tim to add you to Google Cloud
• Ask Tim to add you to runapikey.json on Google Drive
• Get runapikey.json from Google Drive

Helpful Links

• Check Bucket Status
• Check MOVES Workflow Status Here:
• Check Jobs Status Here
• Check Upload Workflow Status Here
• Check CAT Cloud Server Here
• Check Permissions Here
• Check Billing Here
• Check CATSERVER Read-Only Credentials for granddata here. (Need permission)
• Check API Key here. (Need permission)
• Check CATCLOUD Read-Write Credentials for orderdata here. (Need permission)

Key things to test

• Did it work?
• How many minutes did the job? (Eg. what should our max timeout be?)
• What output tables were filled?

Possible Options for fixing include:

• Adding more cpus
• Adding more RAM
• Adding longer timeout limit
• Making any of these conditional on bucket contents

Issue Table

https://docs.google.com/spreadsheets/d/1zETXEDB191QgLDV-sYuQIefUrA00pf77vCoUglH8qfQ/edit?usp=sharing

Please feel free to add.

*Note: CAT pollutants are: c(98, 3, 87, 2, 31, 33, 110, 100, 106, 107, 116, 117).
This corresponds to: CO2 Equivalent (98), Ozone = created when NOx (3) interacts with VOC (87), Carbon Monoxide = 2, Lead (measured by VOC) = 87, Sulfur Dioxide (SO2) = 31, Nitrogen Dioxide (NO2) = 33, PM2.5 = 110, PM10 = 100, plus PM10 - Brakewear 106, PM10 - Tirewear 107, PM2.5 - Brakewear 116, PM2.5 - Tirewear 117

When expanded out to include required pollutant processes, this increases to the list found by:
catr::get_pollutantprocessassoc(c(98, 3, 87, 2, 31, 33, 110, 100, 106, 107, 116, 117))

[ccloss65536]

This is pretty small, but the function trigger_run has the folder parameter repeated twice, which we had to fix to use. I would like to make a pull request fixing it, but I'm not currently allowed

[em843]

This is pretty small, but the function trigger_run has the folder parameter repeated twice, which we had to fix to use. I would like to make a pull request fixing it, but I'm not currently allowed

Just granted access. On the latest version of main, the issue appears to be already fixed for me.