Script-writing workflows

[wmoore]

Document typical script-writing workflows for admins and users. Both for our use in developing and testing the workflow, and for web-site documentation.

Intro

If you are planning to spend a significant amount of time developing scripts to run on an OMERO server, you may find it worthwhile to install an instance of the server on your own machine. This will give you to test scripts under 'user' or 'admin' privileges, and allow you direct access to the various files generated on the server by the scripting service.

Admins

It is assumed that scripts written by a server admin are "trusted" to run on the server without causing any disruption or security risks.

• Write script
• Make sure all required package imports are available on server
• Upload as 'official' script (unique path)
• Run script (identify by path)
• If necessary, check recent files under /OMERO/Files/ for any std-out or std-err output generated by the script.

Users

If you are using a server for which you do not have admin access, you must upload scripts as 'user' scripts, which are not trusted to run on the server machine. The OMERO scripting service will still execute these scripts in a similar manner to official 'trusted' scripts but 'behind the scenes' it uses the client machine to execute the script. This means that any package imports required by the script should be available on the client machine.

• Write script
• Upload script to server (path not unique)
• Run script (identified as most recent with specified path)
• Check returned results for std-err (and std-out)
• Retrieve any std-err and std-out files from the server