Introduction
This document attempts to summarize what work and resources that would be needed to make an effective EXO 200 analysis environment on the SRCF computing facility, under the assumption that this needs to be done without the user doing the analysis needing a SLAC account.
...
In the following discussion we have assumed that the user is able to get an SRCF account and compute resources through EXO's affiliation with Stanford (Giorgio Gratta, PI).
Access to documentation and web applications
This can be provided by setting up a "collaboration enclave account" (== crowd account) for the user. Under the assumption that setting up such an account is allowable (and I already checked with Eric Shupert and he assures me it is) then everything we need is already available.
Work required: negligible
Access to source code
The EXO 200 source code is stored in a subversion code repository at SLAC. Up to now we have used "svn+ssh" access to the repository since this is the simplest mechanism when all users already have SLAC unix accounts. For other experiments we have used direct subversion access, which only requires that users have an entry in a list of "virtual" accounts, very similar to the "collaboration enclave account" described above. Assuming that this access is acceptable then setting up similar access for EXO account should be straightforward.
Work required: <1 day (not including any required cyber security review)
Access to data
The EXO-200 data is currently stored on servers with private IP addresses. There are several possible ways of making the data available at SRCF
...
Resources required: 1-2 weeks, depending on what issues are discovered. Would likely require assistance for SRCF/SLAC networking groups, and xrootd team (Andy Hanushevsky+Wilko Kroeger). Access to a server (or servers) to run xrootd proxy at SLAC and/or SRCF would be required.
Access to batch resources
Batch resources can hopefully be made available via the SRCF. For these resources to be effective we need to reproduce the environment available on the SLAC batch farm. This includes:
...
Resources required: Server at SRCF to run Jenkins, plus disk space for builds (~200GB). Work required to set up server, and verify that EXO software runs as expected ~1 week.
Conclusion
Setting up such a facility does seem possible, and would require fairly modest resources, but nonetheless these resources would need to be identified (presumably with some budget code to cover the work). In addition to ensure the required work happens in a timely way some effort would need to be put into spearheading and coordinating the work.