About

The sDL system is a computational system (running in virtual machines deployed on currently 5 servers) based on three main concepts

  1. Scientists do not need to install software for interacting with packages, in order to process their data and obtain the resulting computations;
  2. Each interaction is made through text files (with the sDL file format) and data files transfers from client<->servers are managed automatically;
  3. Scientists do not need to care if the package runs in a Linux, OSX, or Windows ecosystem. The sDL client makes everything transparent to the user.

The uppercase letters mean Dynamic encapsulation Language, the small s stands for any of the following (at your own choice): scientific, simple, stratified, strange, seamless, seminal, sequential, stupefy, or sexy. The developers tried to focus on the first three meanings where stratified stands for several layers of abstraction. In fact, there are one template layer, two preprocessing layers, one section group and one namespace layer. However, when you don’t need it is goes back to be just a simple text file which do it all.

Other features:

  • Users may control and add their own packages into the sDL system, directly from a sDL project;
  • Each sDL project may have the following documentation folders (available in this website): (a) a public folder that appears under “User’s Public Projects”, see below; (b) a private folder with access control; (c) package and commands simple documentation generation folders; and (d) folders to generate “how to use examples” for any installed package appearing in the package documentation page;
  • Each sDL project has embedded the following mechanisms that allow to: (a) run sDL files periodically; (b) log of warnings and errors; (c) inter-project messaging; (d) runtime monitoring of resources/process; (e) e-mail and mobile handler alerts.

Change Log

Version 1.1

2019/01/05 - Added packages: uParser, uRun
2019/01/04 - Added online demos/sDL-pck mechanism
2019/01/03 - Added rPrism package
2018/12/28 - Added uConfig package
2018/12/13 - Servers vm2,...,vm5 were upgraded
2018/11/17 - Added packages: cOPT, erSTATUS, GetSend, monVARS
2018/11/15 - Several improvements
2018/07/03 - Added PGInv package

Version 1.0

2017/07/19 - Added GIT support to package-code
2017/02/12 - Several minor improvements in sDL-docs
2016/05/07 - Improvements of webservices
2016/05/06 - Improvements and bug fixes of the sDL clients (Linux/Darwin)
2016/05/05 - Integration of Torque/PBS with sDL and comm port reduction
2016/05/03 - Integration of cluster statistics on "Status Board" (iOS/app): nodes loads, calc hours, calc calls, node packages, resources, etc.
2016/04/18 - Added packages pHL-MT, ExtremeVA, and SignalDecomp
2016/04/15 - Improvements in deploying packages
2016/04/14 - Users may add and control their own packages (sDL-package) via the package uPackage
2016/04/10 - fDL improvements and bug fixes
2016/04/05 - Servers vm4 and vm5 went live
2016/04/04 - Server vm3 went live
2016/03/20 - Packages access restructured
2016/03/04 - The fDL field/template functionality was added
2016/03/03 - Projects and packages may produce their own documentation (sDL-docs) via the package uDoc
2016/03/01 - Server vm2 went live
2016/02/28 - Security through several control layers (e.g. user, prj, package, dropbox)
2016/02/01 - Added packages: LearnPred, prepDATA, pHL-RT, pHL-SV, rDATA
2016/02/22 - sDL documentation system (via sphinx)
2016/02/17 - Server vm1 went live
2016/02/15 - Implementation and deploy of webservices
2016/02/13 - Implementation of client for Linux and Mac (sDL app)
2016/01/18 - Implementation of server tools (sDL-remote, sDL-exec, sDL-run, sDL-code)