Oas installation guide

You can connect to the container using the following command:. If you want to copy case1 from the VIBE container into you working directory, you can do:. Once you launch the job, a window should pop up to specify the properties of the new connection.

In the Host field, write localhost. In the User field, write root. Back on the New Connection window, under Advanced type in the Port field. The container will still run even after you exit ICE. You will need to stop and remove it yourself using:. To check that the container has been removed, type:. This section describes the simulation launch procedure using command line as opposed to using integrated computation environment ICE which is detailed in the next section.

As an example the coupled electrochemical-electrical-thermal modeling of a prismatic cell case 6 is considered here. The structure of the directory case6 is shown below. The input directory contains mesh file Exodus file of the geometry as well as key-value pair input file to set up material constants in simulation models. The names of the keys in the input file are to a great extent self-explanatory. In the above example, the block of electrochemical model parameters represents the NTG model setup.

A slightly different setup is required when the Pseudo 2D model represented by DualFoil subroutine is used. The first element of the vector represents the order of the polynomial that describes impedance Y or OCP U as a function of depth of discharge. If the discharge curves at of the cell different temperatures are available, the corresponding fits can be made bi-polynomial in which case the degree of polynomial in temperature is described by the second element of the vector.

In case when the thermal behavior data are not available, this member is simply set to zero, as in the above example. YPolyCoefficients and YPolyCoefficients are the vectors containing the coefficients of the corresponding polynomial fits. Once the input file has been modified accordingly and saved the simulation parameters can be configured. This is done within the simulation configuration file SimulationName. If a different model is desired this can be changed here. While the example case6 uses NTG model to describe electrochemistry, this can be changed to Pseudo 2D component DualFoil if needed and if all material constants required for DualFoil code to run are available.

The corresponding component specification can be added to the configuration file, for instance:. In this case, the DualFoil Fortran code requires two input files that need to be placed in the input directory of the simulation case. More on the DualFoil code description and requirements can be found at cchem. The last set of parameters in the simulation config file defines the time marching. Two ways of setting up the time step can be implemented. Time is specified in minutes. EXPLICIT method allows using non-uniform size of time steps and is useful where cell potential changes abruptly compared to otherwise smooth profiles where a large time step is sufficient to progress the simulation.

This mode must be used with dynamic discharge option. Once the input files have been edited and simulation configuration has been set, the simulation case6 in virtual machine BatterySim in this example can be launched from the command line by running the following line from the simulation case directory:. When simulation completes the results can be found in work directory where they are arranged by the simulation component.

The corresponding state file named cphit. This starts the visualization software where the simulation results can be loaded as a silo database Fig. Clicking on the Draw button will create a plot in the output window Fig. Rotation, zoom, slicing, transforms, lighting, etc.

More on this software can be found at wci. The plot in Fig. Any of the above simulations can be launched either from command line as described in this section or using ICE as described in the Appendix B. This section provides the tutorial on setting up and running a battery simulation using ICE. It is encouraged that the user becomes familiar with the VIBE directory structure by studying Appendix A first and launching a simulation from command line.

Overall the workflow in ICE consists of:. We created several predefined simulation cases dealing with different cell geometries: unrolled cell sandwich, rolled cylindrical cell, pouch cell and module of four pouch cells.

The case of 4. In this Perspective, ICE provides three options for creating new items. This will launch a dialog prompting you to select a task or Item to create see Fig. You can now edit the parameters if for instance a different number of time steps or different total time is desired. Time Loop Data window Fig 21a, b allows you to select the battery geometry, time stepping scheme, components taking part in the simulation and global configuration.

The Ports Master window Fig. Input directories containing meshes are also specified here. For now leave all the parameters with their default values and click Go!. The key-value pair input file contains numerical parameters necessary for simulation, such as material constants, boundary conditions and coefficients of polynomials when NTG model is used to represent electrochemical component.

The file with default values corresponding to the pouch cell simulation is displayed for edit Fig. The keys are explained in Appendix A. The default simulation represents a discharge of 4. These settings can be edited here if different BC or different polynomials for NTG model are desired. For now accept the default values case6 by clicking Go!.

Once opened, you will be able to review the input file generated. Once the appropriate input files have been generated, launching a simulation is a relatively simple task. Select Caebat Launcher Fig. A form will appear in the main ICE workbench area Fig. The first piece of necessary information is to specify an input file. If you are launching on a remote machine, also be sure that you have appropriate privileges for the CAEBAT install directory.

Lastly, use the Process menu in the upper right-hand corner; select the Launch the Job task from the drop- down menu and click the Go! As the simulation progresses the console window will display different information related to each component being executed in sequence. The simulation is finished when the Done!

The first step is to unzip the files V The rest of the FMW installation is, selecting the installation type, verifying the prerequisites and checking the installation summary. An important step, if you want to reproduce the same installation via script in other environments is to save the response file. The file in the following command named fmw. After installing, we need to apply the patch which was downloaded from e-delivery. To do that, we simply need to unzip the V Again, you may want to save the response file for later in case you want to reproduce the silent installation in another server.

Here are some examples of referencing tags based on their location:. Use the Pump tag for the button, it is a Boolean data type. That way the button text will be something more meaningful than simply True or False. Set it to Pump. The BackgroundFalse and BackgroundQualityBad properties control the background color for when the value is false and bad quality.

This specifies what value to change when the button is clicked. Click the ellipse next to the Needles property. This will open the Needles Collection dialog box. Click the Add button. If enabled, Velero will create a backup of your cluster once every night and upload it to the S3 storage you configure.

This includes:. Technically speaking, it will back up all Kubernetes namespaces in your cluster, except velero itself; this includes things like which applications are installed, including their version number and installation-time settings;. Chat chat history, etc. A single exception to this is Prometheus data statistics of system properties , which takes up a lot of space and we consider not valuable enough to back up.

Then continue with the installation procedure as described below. At the end of the installation procedure, you have to install the velero application.

Before you can start, you need to execute a few commands from the installation directory on your provisioning machine. This installs the core of OpenAppStack into your cluster. After the script completes, you can install applications by running the other installation scripts in the install folder.