You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
There is code that should be wrapping all data placed into the task's output folder into a zip file, uploading it to s3 for storage, providing a link on task history.
This feature cannot be disabled, but for some reason it is not working
# TODO: someday, optimize s3 stuff so we don't have this hanging out in-memory...
save_output_file(forest_task, f.read())
On our production server there are functional historical forest tasks 2023-12-1 - 2024-4-9, and then they stop.
Maybe there were changes to the file output in forest?
@hydawo This was from the meeting earlier today, the raw data output from sycamore (and all forest task runs) should be available via a separate link, but that link is not present.
@hackdna@MMel099 Can you point me to the code or documentation on where and what output files are supposed exist when running forest tree, and how it differs between trees. (I'm not ruling out errors in my code.)
The text was updated successfully, but these errors were encountered:
Forest on Server
[] Update Forest
[] Modify headers on server to match local forest script headers (specifically Jasmine & Oak) - @biblicabeebli is this difficult? If so, we can consider modifying the headers in local forest script to match server headers
[] Remove "GPS Data Missing Duration" column entirely for Jasmine output
[] Modify order of columns in large Forest output CSV
[] Remove spaces in column header titles
Local Forest Script
[] modify date output from 3 columns (y, m, d) to single column (mm/dd/yyyy)
[] adding Physical Circadian Rhythm code to Jasmine
[] add Oak concatenate function
Final Tasks
[] Update Forest on server (after all modifications above)
[] Make any necessary modifications to Forest Wiki
There is code that should be wrapping all data placed into the task's output folder into a zip file, uploading it to s3 for storage, providing a link on task history.
This feature cannot be disabled, but for some reason it is not working
beiwe-backend/services/celery_forest.py
Lines 446 to 467 in e880bc0
On our production server there are functional historical forest tasks 2023-12-1 - 2024-4-9, and then they stop.
Maybe there were changes to the file output in forest?
@hydawo This was from the meeting earlier today, the raw data output from sycamore (and all forest task runs) should be available via a separate link, but that link is not present.
@hackdna @MMel099 Can you point me to the code or documentation on where and what output files are supposed exist when running forest tree, and how it differs between trees. (I'm not ruling out errors in my code.)
The text was updated successfully, but these errors were encountered: