![]() The reasoning behind providing this stub implementation is that simulation developer can compile their simulation codes linked with Catalyst without requiring a ParaView SDK build. provides a stub implementation which is simply does nothing. ![]() The following only applies to Catalyst V2. That has been installed from source from here:Ĭould it be a problem ? if not what is the procedure to make these examples working ? One thing I notice in compilation is that the examples are linked with /usr/local/lib64/libcatalyst.so.2 All look good but no output … or nothing interesting happen. I checked the that the example was looping putting a cout in the loop, I checked that the script was set correctly in the adaptor with a cout. shouldn’t it print every time steps ? The same happen for all the other examples. The program run for the time steps it has to run, but nothing is printed from the catalyst_pipeline.py. When I try to make them running in the folder bin … for exampleĬxxMultiChannelInputExampleV2 …/…/catalyst_pipeline.py (same if I give the full path) While I can compile them without problems. Unfortunately I am having an hard time to make them working. I am now approaching Catalyst V2 examples that look much simpler and clean. The one I tried all produce output or can visualize live in Paraview. We will now work through an example, using data2pvd to visualise a simple data set produced using the example code ChuteDemo.I played with Catalyst V1 examples … I compiled the examples and played with them to see how they works. ![]() In order to visualise the data using Paraview, the data2pvd tool can be used to convert the ‘.data' files output by Mercury into a '.pvd' Paraview datafile and several VTK (.vtu) files. On Ubuntu, it can simply be installed by typing sudo apt-get install paraview ParaView may be downloaded from and installed by following the relevant instructions for your operating system. a direct, visual representation of the motion of all particles within the system produced. We begin by discussing the manner in which Mercury data can simply be ‘visualised’ - i.e. its current position in three dimensions \(\vec)\) denote unit vectors normal and tangential to the contact plane, respectively.Ĭontact properties reported in the fstat file a non-spherical particle is shown to visualise that the branch vector c-ri is not necessarily parallel to the normal vector n.These parameters are output in the following order: rx, ry, rz, vx, vy, vz, rad, alpha, beta, gamma, omex, omey, omez, infoįor each particle, we are given information regarding This output is then followed by a series of N subsequent lines, each providing information for one particle within the system. the maximal and minimal spatial boundaries defining the computational volume used in the simulations, xmin, ymin, zmin, xmax, ymax, zmax.the time step time when the output was written, and.This first line is structured as below: N, time, xmin, ymin, zmin, xmax, ymax, zmaxįor each timestep, we are given information regarding The files are formatted as follows: at each time step, a single line stating the number of particles in the system ( N). The data file is perhaps the most useful and versatile of the three, as it provides full information regarding the positions and velocities of all particles within the system at each given time step. Data is written at predefined time steps, with the system’s total gravitational ( ’ene_gra’) and elastic ( ’ene_ela’) potential energies and translational ( ’ene_kin’) and rotational ( ’ene_rot’) kinetic energies being shown alongside the system’s centre of mass position in the x, y and z directions ( ’X_COM’, ’Y_COM’ and ’Z_COM’, respectively).Īt each time step, the data is output as follows: time ene_gra ene_kin ene_rot ene_ela X_COM Y_COM Z_COM The simplest of the three file types is the ‘.ene’ file, which allows us to interpret the time evolution of the various forms of energy possessed by the system. Thus, execution will create output files named ‘example.data’, ‘example.fstat’ and ‘example.ene’ (other files such as ‘example.restart’ and ‘example.stat’ might be created, which will be discussed in later sections). ![]() The output file name is set using DPMBase::getName the MercuryDPM convention is that the name of the output file names should be equal to the name of the source file. This page is divided in two parts:Įach MercuryDPM executable produces three main output files, with the extensions ‘.data’, ‘.fstat’ and ‘.ene’.įor instance, building the source file example.cpp will create an executable named example. Mercury produces data regarding a wide range of system parameters and, as such, there exist a variety of manners in which this data may be obtained and processed. Having explained in the previous section the how to run a Mercury driver code, we next explain the form of the data output, and describe how relevant information may be extracted from this data.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |