Consensus statement from the 2014 International Microdialysis Forum.

Microdialysis enables the chemistry of the extracellular interstitial space to be monitored. Use of this technique in patients with acute brain injury has increased our understanding of the pathophysiology of several acute neurological disorders. In 2004, a consensus document on the clinical application of cerebral microdialysis was published. Since then, there have been significant advances in the clinical use of microdialysis in neurocritical care. The objective of this review is to report on the International Microdialysis Forum held in Cambridge, UK, in April 2014 and to produce a revised and updated consensus statement about its clinical use including technique, data interpretation, relationship with outcome, role in guiding therapy in neurocritical care and research applications.We gratefully acknowledge financial support for participants as follows: P.J.H. - National Institute for Health Research (NIHR) Professorship and the NIHR Biomedical Research Centre, Cambridge; I.J. – Medical Research Council (G1002277 ID 98489); A. H. - Medical Research Council, Royal College of Surgeons of England; K.L.H.C. - NIHR Biomedical Research Centre, Cambridge (Neuroscience Theme; Brain Injury and Repair Theme); M.G.B. - Wellcome Trust Dept Health Healthcare Innovation Challenge Fund (HICF-0510-080); L. H. - The Swedish Research Council, VINNOVA and Uppsala Berzelii Technology Centre for Neurodiagnostics; S. M. - Fondazione IRCCS Cà Granda Ospedale Maggiore Policlinico; D.K.M. - NIHR Senior Investigator Award to D.K.M., NIHR Cambridge Biomedical Research Centre (Neuroscience Theme), FP7 Program of the European Union; M. O. - Swiss National Science Foundation and the Novartis Foundation for Biomedical Research; J.S. - Fondo de Investigación Sanitaria (Instituto de Salud Carlos III) (PI11/00700) co-financed by the European Regional Development; M.S. – NIHR University College London Hospitals Biomedical Research Centre; N. S. - Fondazione IRCCS Cà Granda Ospedale Maggiore Policlinico.This is the final version of the article. It first appeared from Springer via http://dx.doi.org/10.1007/s00134-015-3930-

Consensus statement from the 2014 International Microdialysis Forum

This is the final version of the article. It first appeared from Springer via http://dx.doi.org/10.1007/s00134-015-3930-yMicrodialysis enables the chemistry of the extracellular interstitial space to be measured. Use of this technique in patients with acute brain injury has increased our understanding of the pathophysiology of several acute neurological disorders. In 2004 a consensus document on the clinical application of cerebral microdialysis was published. Since then there have been significant advances in the clinical use of microdialysis in neurocritical care. The objective of this review is to report on the International Microdialysis Forum held in Cambridge, UK, in April 2014 and to produce a revised and updated consensus statement about its clinical use including technique, data interpretation, relationship with outcome, role in guiding therapy in neurocritical care and research applications.We gratefully acknowledge financial support for participants as follows: P.J.H. - National Institute for Health Research (NIHR) Professorship and the NIHR Biomedical Research Centre, Cambridge; I.J. ? Medical Research Council (G1002277 ID 98489); A. H. - Medical Research Council, Royal College of Surgeons of England; K.L.H.C. - NIHR Biomedical Research Centre, Cambridge (Neuroscience Theme; Brain Injury and Repair Theme); M.G.B. - Wellcome Trust Dept Health Healthcare Innovation Challenge Fund (HICF-0510-080); L. H. - The Swedish Research Council, VINNOVA and Uppsala Berzelii Technology Centre for Neurodiagnostics; S. M. - Fondazione IRCCS C? Granda Ospedale Maggiore Policlinico; D.K.M. - NIHR Senior Investigator Award to D.K.M., NIHR Cambridge Biomedical Research Centre (Neuroscience Theme), FP7 Program of the European Union; M. O. - Swiss National Science Foundation and the Novartis Foundation for Biomedical Research; J.S. - Fondo de Investigaci?n Sanitaria (Instituto de Salud Carlos III) (PI11/00700) co-financed by the European Regional Development; M.S. ? NIHR University College London Hospitals Biomedical Research Centre; N. S. - Fondazione IRCCS C? Granda Ospedale Maggiore Policlinico

MGMT 401 Organizational Behavior

Course syllabus for MGMT 401A Organizational Behavior Course description: Analyzes the behavior of people in organizations. Discusses organizational behavior, communication, and decision making

POLS 863 Seminar in American Institutions and Values

Course syllabus for POLS 863 Seminar in American Institutions and Values Course description: This course addresses the moral dimension of discretionary choices made by public managers. The course considers how moral questions - choices among values - apply to concrete decisions of public authorities. The primary objective of the course is to train students in serious moral analysis. This requires the attainment of skill methods of thinking and writing (logic and rhetoric). The instructor will assume that the way the student writes is the way he or she thinks. Therefore more than half of the student\u27s grade for the course will depend upon how well he or she writes. U.S. Supreme Court opinions on the core values of the American Republic of freedom, property, and equality are studied for examples of how broad, value-laden concepts can have practical meaning as guides to the resolution of actual problems that administrators may face. These opinions will serve as examples both of the content of values AND of methods of analysis, exposition, and argumentation

MGMT 860 Issues in Public and Private Management

Course syllabus for MGMT 860 Issues in Public and Private Management Course description: This course offers advanced consideration of organizational issues such as decision making, leadership and ethics. Students apply concepts and findings both to business and to government organizations

sylabs/singularity: SingularityCE 4.0.0

We are pleased to announce the availability of SingularityCE 4.0.0. This is a new major version, with the new OCI-mode becoming fully supported and expanded to use OCI-SIF images. v4.0.0 also introduces a number of CLI improvements, templating support for definition files, improved platform/architecture handling for OCI images, and much more. Please review the changelog carefully, as it highlights behavior changes that may impact some workflows. You may also wish to read the 'What's new in SingularityCE 4.0' sections of the: SingularityCE User Guide SingularityCE Adminstrator Guide OCI-mode Singularity 4 introduces OCI-mode as a fully supported feature. It is enabled by using the --oci flag with the run / shell / exec / pull commands, or by setting oci mode = yes in singularity.conf. In OCI-mode: Container images from OCI sources will be pull-ed to an OCI-SIF file. An OCI-SIF file encapsulates the OCI image configuration and squashed filesystem using an OCI, rather than Singularity specific, structure. The run / shell / exec commands use a low-level OCI runtime (crun/runc) for container execution. Default operation is compatible with other OCI tools, similar to using --compat in Singularity's non-OCI native mode. OCI-modes support running existing Singularity non-OCI-SIF images, and can be made to imitate native mode default behavior by using the --no-compat flag. OCI-mode changes from 3.11 to 4.0 include: run / shell / exec in OCI-mode now includes support for the following existing CLI flags: --add-caps --drop-caps --keep-privs --no-privs --overlay from directories, bare squashfs and extfs images. --workdir --scratch --no-home --no-mount (dev cannot be disabled in OCI mode) --no-umask (with --no-compat) --writable-tmpfs (with --no-compat) Added --device flag to "action" commands (run/exec/shell) when run in OCI mode (--oci). Currently supports passing one or more (comma-separated) fully-qualified CDI device names, and those devices will then be made available inside the container. Added --cdi-dirs flag to override the default search locations for CDI json files, allowing, for example, users who don't have root access on their host machine to nevertheless create CDI mappings (into containers run with --fakeroot, for example). A container run as root, or with --fakeroot, has OCI default effective/permitted capabilities. An --env-file is evaluated with respect to the host environment, to match native mode behaviour. If the kernel does not support unprivileged overlays, OCI-mode will attempt to use fuse-overlayfs and fusermount for overlay mounting and unmounting. Support for thee SINGULARITY_CONTAINLIBS env var, to specify libraries to bind into /.singularity.d/libs/ in the container. Support for running OCI-SIF images directly from docker://, http://, https:// and oras:// URIs. A new --no-compat flag can be used with OCI-mode to mirror singularity's historic native mode behavior on a variety of settings, instead of setting them the way other OCI runtimes typically do: $HOME, /tmp, /var/tmp are bind mounted from the host. The full /dev is bind mounted from the host, unless mount dev = minimal in singularity.conf (requires crun, not applied with runc). bind path entries in singularity.conf are mounted into the container. The current working directory is mounted into the container, and is the entry point into the container. The container is read-only unless --writable-tmpfs is also used. The host umask is propagated into the container, unless --no-umask is also used. When a native (non-OCI-SIF) image is run in OCI-mode, environment variables will be shell evaluated on container startup. The pull command now accepts a new flag --oci for OCI image sources. This will create an OCI-SIF image rather than convert to Singularity's native container format. OCI-SIF containers can be pushed/pulled to/from OCI registries as single file artifacts using oras:// URIs. OCI-SIF containers can be pushed/pulled to/from registries as OCI images, with a single squashfs layer, using docker:// URIs. A new oci mode directive in singularity.conf can be set to true to enable OCI-mode by default. It can be negated with a new --no-oci command line flag. See the admin guide and user guide for full requirements of OCI-mode and usage information. Changed defaults / behaviours Packages / Requirements RPM packages now use /var/lib/singularity (rather than /var/singularity) to store local state files. Bash completions are now install to the modern share/bash-completion/completions location, rather than under etc. The --vm and related flags to start singularity inside a VM have been removed. This functionality was related to the retired Singularity Desktop / SyOS projects. Singularity uses squashfuse_ll / squashfuse, which is now built from a git submodule unless --without-squashfuse is specified as an argument to mconfig. When built with --without-squashfuse, squashfuse_ll or squashfuse will be located on PATH. Version 0.2.0 or later is required. CLI The commands related to OCI/Docker registries that were under remote have been moved to their own, dedicated registry command. Run singularity help registry for more information. The remote list subcommand now outputs only remote endpoints (with keyservers and OCI/Docker registries having been moved to separate commands), and the output has been streamlined. Adding a new remote endpoint using the singularity remote add command will now set the new endpoint as default. This behavior can be suppressed by supplying the --no-default (or -n) flag to remote add. The keyserver-related commands that were under remote have been moved to their own, dedicated keyserver command. Run singularity help keyserver for more information. Improved the clarity of singularity key list output. --cwd is now the preferred form of the flag for setting the container's working directory, though --pwd is still supported for compatibility. Runtime Behaviour The way --home is handled when running as root (e.g. sudo singularity) or with --fakeroot has changed. Previously, we were only modifying the HOME environment variable in these cases, while leaving the container's /etc/passwd file unchanged (with its homedir field pointing to /root, regardless of the value passed to --home). With this change, both the value of HOME and the contents of /etc/passwd in the container will reflect the value passed to --home. Bind mounts are now performed in the order of their occurrence on the command line, or within the value of the SINGULARITY_BIND environment variable. (Previously, image-mounts were always performed first, regardless of order.) Default OCI config generated with singularity mount no longer sets any inheritable / ambient capabilites, matching other OCI runtimes. singularity oci mount now uses, and requires, squashfuse_ll or squashfuse to mount a SIF image to an OCI bundle. Note that squashfuse_ll is built with singularity unless --without-squashfuse is passed to mconfig. The current working directory is created in the container when it doesn't exist, so that it can be entered. You must now specify --no-mount home,cwd instead of just --no-mount home to avoid mounting from$HOME if you run singularity from inside HOME. If the path of the current working directory in the container and on the host contain symlinks to different locations, it will not be mounted. New Features & Functionality Templating support for definition files: users can now define variables in definition files via a matching pair of double curly brackets. Variables of the form {{ variable }} will be replaced by a value defined either by a variable=value entry in the %arguments section of the definition file, or through new build options --build-arg or --build-arg-file. Added --secret flag (shorthand: -s) to key remove subcommand, to allow removal of a private key by fingerprint. Added --private as a synonym for --secret in key list, key export, and key remove subcommands. The remote status command will now print the username, realname, and email of the logged-in user, if available. The cache commands now accept --type oci-sif to list and clean cached OCI-SIF image conversions of OCI sources. The instance start command now accepts an optional --app argument which invokes start script within the %appstart section in the definition file. The instance stop command still only requires the instance name. A new --no-pid flag for singularity run/shell/exec disables the PID namespace inferred by --containall and --compat. A new --platform flag can be used to specify an OS/Architecture[/Variant] when pulling images from OCI or library sources. When pulling from library sources the optional variant is ignored. The --arch flag can now be used to specify a required architecture when pulling images from OCI, as well as library sources. Execution flows that unpack an image into a temporary sandbox dir can now be disabled, by setting "tmp sandbox = no" in singularity.conf or by passing --no-tmp-sandbox to the relevant run / shell / exec command. Developer / API Support for image driver plugins, deprecated at 3.11, has been removed. Unprivileged kernel overlay is supported without a plugin. In singularity.conf, the image driver directive has been removed, and enable overlay no longer supports the driver option. Changes in pkg/build/types.Definition struct. New .FullRaw field introduced, which always contains the raw data for the entire definition file. Behavior of .Raw field has changed: for multi-stage builds parsed with pkg/build/types/parser.All(), .Raw contains the raw content of a single build stage. Otherwise, it is equal to .FullRaw. The SingularityCE go module is now github.com/sylabs/singularity/v4, reflecting the major version of the application. Bug Fixes Fix interaction between --workdir when given relative path and --scratch. Set correct HOME in --oci mode when mount home = no in singularity.conf. Lookup and store user/group information in stage one prior to entering any namespaces to fix issue with winbind not correctly lookup user/group information when using user namespace. Caching of OCI images is now architecture aware. This fixes behaviour where a user's home directory is shared between systems of different architectures. Fix compilation with the mconfig -b option (custom builddir). Thanks / Reporting Bugs Thanks to our contributors for code, feedback and, testing efforts! As always, please report any bugs to: https://github.com/sylabs/singularity/issues/new If you think that you've discovered a security vulnerability please report it to: [email protected] Have fun! Downloads Source Code Please use the singularity-ce-4.0.0.tar.gz download below to obtain and install SingularityCE 4.0.0. The GitHub auto-generated 'Source Code' downloads do not include required dependencies etc. Packages RPM / DEB packages are provided for: Ubuntu 20.04 (focal) Ubuntu 22.04 (jammy) RHEL/CentOS 7 (el7) RHEL/CentOS/AlmaLinux/Rocky 8 (el8) RHEL/CentOS/AlmaLinux/Rocky 9 (el9) These packages were built with Go 1.21.