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
When "download data" on the app is used, it currently pulls the pre-existing sessionMetaData.yaml from the session. However, this file seems to always have the key gender_mf with associated with the value m when downloading from the app.
Some possibly useful parts of the code to trace the calls:
Figure out a strategy for dealing with older yaml files. Determine if it would be costly to update the .yaml file on AWS each down Download Data is used
When "download data" on the app is used, it currently pulls the pre-existing
sessionMetaData.yaml
from the session. However, this file seems to always have the keygender_mf
with associated with the valuem
when downloading from the app.Some possibly useful parts of the code to trace the calls:
To-dos:
Find and fix where in core where static/neutral trial creates the .yaml file and posts to AWS(this might have been fixed by [Under review] - Fix problem with gender_mf field in downloaded files. opencap-core#208)The text was updated successfully, but these errors were encountered: