I am working on a model of hot water storage developed in Buildings library of Modelica. Using Dymola to simulate the model by Dassl, I changed time step of simulation from 1s to 1200s, but I have not seen any change in simulation result. Is it something related to the solver? I would appreciate if you could help.
Variation in Time Step Size does not affect the simulation results in Dymola
354 Views Asked by AJodeiri At
1
There are 1 best solutions below
Related Questions in SIMULATION
- Issues in Migration of RISCV Test Harness from VCS to Questasim Simulator
- Queue Scenario Help Getting Started
- Writing a simulation program in Python
- Java Card applet EEPROM vs RAM testing
- Simulate the use of a website with a client
- Verilog simulation x's in output
- Time step independence of Molecular Dynamics code
- How to code a arrival generator with a varying intensity rate
- Is it possible to build a heatmap from point data at 60 times per second?
- Verilog Testbench constant exp and pram compilation and simulation errors
- Evaluation / Simulation of existing python program
- Pause and resume threads that are sleeping Java
- Simultaneous object interaction in javascript
- Faster alternative to populating a pre-allocated data frame using a for-loop
- Simulating a game where each player has a different probability of winning?
Related Questions in MODELICA
- modelica: compute minimum/maximum of continuous variable over time
- FMU Export of Python Code or Python Interface with FMI Standard for Use in EnergyPlus Co-Simulation
- Managing of Navier-Stokes PDEs by means of SBF in Dymola
- Simulation of Electrical drives using Dymola
- External Functions: Alternative Method to use .dll from a C-script
- alternative to sample function with varying sampling range
- Why has an FMU exported as FMI1 different statistics than if exported as FMI2
- ValveLinear Model Modelica Standard Library - Working Principle
- Change output file format to *.csv using dymosim.exe instead of *.mat
- Setting boolean for a time period
- Modelica "Resolve error : no match for overloaded binary operator "
- Why same OpenModelica code behaves differently in two files?
- Vary frequency of sin voltage source in Modelica
- Modelica: model in a model and Instantiation
- Modelica.Media.R134a Error
Related Questions in TIMESTEP
- ValueError: Can not squeeze dim[1], expected a dimension of 1
- maximum time step of IDA solver in Open Modelica
- Python3.7 function to plot datetime from timestep of netCDF4
- NCO: is there any one-line command to change the index of time dimension as a whole array (not by for-loop)?
- Is it possible to update funcion variables every time it's been called?
- Variation in Time Step Size does not affect the simulation results in Dymola
- Combining timesteps in R
- Is there an NCO command to change the time stamp of a variable in a netcdf?
- step doubling Runge Kutta implementation stuck shrinking stepsize to machine precision
- Keras loaded model output is different from the training model output
- How do I backpropagate gradients onto the input of time step 1 in an LSTM network in Tensorflow?
- What is the difference between timesteps and features in LSTM?
- Progressive point to point walk plotting in R
- How to set the timeStep for execution of specific code snippet?
- scipy.integrate.odeint time dependend stepsize
Trending Questions
- UIImageView Frame Doesn't Reflect Constraints
- Is it possible to use adb commands to click on a view by finding its ID?
- How to create a new web character symbol recognizable by html/javascript?
- Why isn't my CSS3 animation smooth in Google Chrome (but very smooth on other browsers)?
- Heap Gives Page Fault
- Connect ffmpeg to Visual Studio 2008
- Both Object- and ValueAnimator jumps when Duration is set above API LvL 24
- How to avoid default initialization of objects in std::vector?
- second argument of the command line arguments in a format other than char** argv or char* argv[]
- How to improve efficiency of algorithm which generates next lexicographic permutation?
- Navigating to the another actvity app getting crash in android
- How to read the particular message format in android and store in sqlite database?
- Resetting inventory status after order is cancelled
- Efficiently compute powers of X in SSE/AVX
- Insert into an external database using ajax and php : POST 500 (Internal Server Error)
Popular Questions
- How do I undo the most recent local commits in Git?
- How can I remove a specific item from an array in JavaScript?
- How do I delete a Git branch locally and remotely?
- Find all files containing a specific text (string) on Linux?
- How do I revert a Git repository to a previous commit?
- How do I create an HTML button that acts like a link?
- How do I check out a remote Git branch?
- How do I force "git pull" to overwrite local files?
- How do I list all files of a directory?
- How to check whether a string contains a substring in JavaScript?
- How do I redirect to another webpage?
- How can I iterate over rows in a Pandas DataFrame?
- How do I convert a String to an int in Java?
- Does Python have a string 'contains' substring method?
- How do I check if a string contains a specific word?
First my assumtion: With "time step" you are referring to the "Interval length" shown in the screenshot below.
If that is the case, this is totally correct behavior. The "Output interval" is independent from the simulation itself. Variable step solvers like DASSL choose their step-size on their own and interpolate the output from the computed points - which are likely computed at different points in time. You can check the steps taken by the solver using the "Simulation Analysis" function of Dymola.
If you want to influence the actual steps taken by the solver you have some other possibilities:
Advanced.Simulation.StepSizeMaxlimits the upper bound or the step sizeAdvanced.Simulation.StepSizeMinlimits the lower bound or the step sizeAdvanced.Simulation.StepSizeStartsets the initial step sizeBe careful with the Advanced variables, as they can influence performance and stability. Side note: There can be some influence from the "Interval length/Number of intervals" to the simulation result, as DASSL considers this setting when choosing its initial step-size. But this effect can vanish depending on the dynamics.