For instructions on how to connect to a closed zone, see here.
GenomeDK is divided into zones. The open zone resembles traditional high-performance computing systems where data can be moved freely in and out of the system.
For projects with additional security or legal requirements, GenomeDK provides closed zones. A closed zone is an additional layer of security on top of our existing security solutions.
A zone is not a “cloud” (we’re not even sure exactly what that means). Cloud solutions are flexible, but most users don’t need that flexibility. The flexibility also comes at a cost: very bad efficiency. With most cloud solutions, you will have to allocate a specific amount of ressources up front. If you don’t need all of those ressources all of the time, they will be wasted, but you will still have paid for them.
A closed zone provides:
This comes with the same benefits as using the open zone:
A closed zone is not tied to a single project – one or more project folders belong to the zone, so users in a zone can still organize and share their data via project folders inside the zone.
Users will need a separate account/user for each closed zone they need access to.
If you think that you need a closed zone for your projects, feel free to get in touch.