Giters

AI-SDC / ACRO

Tools for the Automatic Checking of Research Outputs. These are the tools for researchers to use as drop-in replacements for commands that produce outputs in Stata Python and R

Geek Repo:Geek Repo

Github PK Tool:Github PK Tool

Plan to TREs for comment

jim-smith opened this issue · comments

commented

Questions for TRE's to discuss

  1. Is it ok that the. query results don't get written to file until the usr calls acro.finalise()?

    • Has implications for our renaming functionality
    • but what if the user forgets! how do we prompt them?

  2. Imagine a user goes off home, or for lunch etc., so calls finalise to save their work so far.

    • When they come back, do we want to do we want be able to restart a session or start a new one?
    • This has implications for being able to delete things if they decide they don't want them.
    • would TREs prefer to see could we have functionality that let them have a choice here?

  3. (relates to 2) At present we have added timestamps to the end of output names, because of the issue of a second session restarting counting from 0, so over-writing files. What would TREs prefer?

  • we could automatically reload the previous session
    • which might get lengthy if they work over an extended period of time,
    • but would be fine if they organised different stands of work into separate folders
    • is that realistic?
  • does each project get given its own user area or folder/sub-directory?
commented

Do they prefer word doc then copy into their own python environment?
or python code with comments?

---We need a set of questions for them to think about

commented

Goes to
Kate O'Sullivan at Dash/Aberdeen
Amy Tilbrook at Data loch
Pete Stokes & Seb Bacon at OpenSafely (Oxford)
Shahzad and Chris Cole at Dundee/HIC
Michael Sibley at eDRIS (Public Health Scotland)

commented

Closed via email to partners 03/05/2023