Menu
▾
▴
dsol-development — Development mailing list
You can subscribe to this list here.
| 2003 |
Jan
|
Feb
|
Mar
|
Apr
(1) |
May
(4) |
Jun
(20) |
Jul
(6) |
Aug
(8) |
Sep
(4) |
Oct
(4) |
Nov
(13) |
Dec
(4) |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2004 |
Jan
(7) |
Feb
(2) |
Mar
(26) |
Apr
(6) |
May
(7) |
Jun
(12) |
Jul
(2) |
Aug
(2) |
Sep
(4) |
Oct
(2) |
Nov
(1) |
Dec
(4) |
| 2005 |
Jan
|
Feb
(1) |
Mar
(7) |
Apr
(2) |
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
| 2006 |
Jan
|
Feb
(1) |
Mar
(4) |
Apr
(2) |
May
(3) |
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
| 2008 |
Jan
|
Feb
|
Mar
|
Apr
(2) |
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
|
From: Alexander V. <a.v...@tu...> - 2008-04-30 22:06:10
|
Dear Jason, DSOL is alive and kicking. Used in many projects and by a number of commercial companies for their multi-formalism simulations. At Delft University of Technology, DSOL has been and is the core simulator for many projects for many industries. The sourceforge site has indeed not been updated for a long time. We use www.simulation.tudelft.nl instead to post updates and information. Please look there for more info. I will look at the sourceforge site in the next few weeks and update there as well, and make the proper links to the simulation.tudelft.nl website. Kind regards, Alexander Verbraeck ---------------------------------------------------------------------- Prof.dr.ir. Alexander Verbraeck Full Professor Systems and Simulation, Systems Engineering Section Faculty of Technology, Policy and Management Delft University of Technology Jaffalaan 5, NL-2628BX Delft, The Netherlands Phone: +31-15-2783805, Secr: +31-15-2788380, Fax: +31-15-2783429 mailto:a.v...@tu... Priv. mailto:a.v...@gm... URL: http://www.tbm.tudelft.nl/webstaf/alexandv Part-time Research Professor University of Maryland, College Park, USA R.H. Smith School of Business - Department of Transport, Logistics and Public Policy. URL: http://www.rhsmith.umd.edu/ ---------------------------------------------------------------------- _____ From: dso...@li... [mailto:dso...@li...] On Behalf Of Jas...@CH... Sent: 30 April 2008 23:45 To: dso...@li... Subject: [Dsol-development] DSOL progress of late I noticed the last posting is a couple years old and the website seems to be a little out of date. Is DSOL still living and breathing? Just curious if people are using this. I see great potential in the field of water resources simulation modeling. Thanks, Jason JASON LILLYWHITE, P.E. | Water Resources Engineer | CH2M HILL | Salt Lake City, Utah Office | Direct: (801) 350-5240 | Cell: (801) 231-8998 | <mailto:Jas...@ch...> Jas...@ch... |
|
From: <Jas...@CH...> - 2008-04-30 21:44:54
|
I noticed the last posting is a couple years old and the website seems to be a little out of date. Is DSOL still living and breathing? Just curious if people are using this. I see great potential in the field of water resources simulation modeling. Thanks, Jason JASON LILLYWHITE, P.E. | Water Resources Engineer | CH2M HILL | Salt Lake City, Utah Office | Direct: (801) 350-5240 | Cell: (801) 231-8998 | Jas...@ch... <mailto:Jas...@ch...> |
|
From: Francisco H. <fhe...@is...> - 2006-05-24 19:07:06
|
Hi Everybody, I am trying to develop a class that inherits from DSOLApplication, but I can't because I can't initialize objects from the nested class Recent. Can you provide a method that returns an object of this class? e.g. DSOLApplication.getRecent(final String label, final long executionTime); Thank you, Francisco |
|
From: Stijn-Pieter v. H. <s.p...@tu...> - 2006-05-16 10:57:42
|
Sorry if you get this message for the second time or twice. All, The CVS repository on sourceforge has changed. The host has been changed to : dsol.cvs.sourceforge.net Previously this was: cvs.sourceforge.net. Hope this solves the repository problems that you may have encountered the past weeks. Kind regards, Stijn-Pieter van Houten. --------------------------------------------- Ir. S.P.A. van Houten, Researcher Delft University of Technology, the Netherlands Faculty of Technology, Policy and Management Systems Engineering Group Jaffalaan 5, 2628 BX Delft, the Netherlands tel. (+31 |0) 15 2788545 fax. (+31 |0) 15 2783429 mob. (+31 |0) 6 48930745 mailto:S.P...@TU... http://www.tbm.tudelft.nl/webstaf/stijnh Global Supply Chain Games http://www.gscg.org --------------------------------------------- |
|
From: Alexander V. <a.v...@tu...> - 2006-05-12 04:28:18
|
Dear DSOL developers / users, The mail below explains the problems with CVS for sourceforge to download DSOL. In addition to sourceforge fixing their CVS, we will also offer alternative CVS locations to download DSOL shortly. Kind regards, Alexander Verbraeck -----Original Message----- From: SourceForge.net Team [mailto:no...@so...] Sent: 12 May 2006 02:58 To: a.v...@tb... Subject: SUBJECT: SourceForge.net: CVS service offering changes Greetings, You are receiving this mail because you are a project admin for a SourceForge.net-hosted project. One of our primary services, CVS, suffered a series of interrelated, critical hardware failures in recent weeks. We understand how frustrating this CVS outage must be to you and your users; however, our top priority remains preservation of the integrity of your data. The series of CVS hardware failures prompted us to expedite the deployment of planed improvements to our CVS infrastructure, drawing upon much of the knowledge that we gained from our Subversion deployment. Our improved CVS service architecture, which we plan to deploy tomorrow afternoon (2006-05-12), will offer greater performance and stability and will eliminate several single points of failure. The Site Status page (https://www.sf.net/docs/A04) will be updated as soon as the new infrastructure is rolled out. In the interim, please read the important information provided below to learn about how these changes will affect your project. Summary of changes, effective 2006-05-12: 1. Hostname for CVS service Old: cvs.sourceforge.net New: PROJECT_UNIX_NAME.cvs.sourceforge.net This change will require new working copies to be checked out of all repositories (so control files in the working copy will point to the right place). We will be updating the instructions we supply, but instructions that your team has written within documentation, etc. will need to be updated. cvs -d:pserver:ano...@cv...:/cvsroot/gaim co gaim would be changed to cvs -d:pserver:ano...@ga...:/cvsroot/gaim co gaim 2. ViewCVS We are moving from ViewCVS to its successor, ViewVC. ViewVC is currently in use for our Subversion service. 3. Sync delay Old: CVS pserver, tarballs and ViewCVS provided against a separate server which is a minimum of three hours behind developer CVS. New: ViewVC will be provided against developer CVS (it will be current). CVS pserver will be provided against a secondary server (not developer server) with a maximum expected delay of two hours. Follow-up work is planned (this infrastructure takes us 80% of the way) to essentially eliminate the sync delay. 4. Read-only rsync service As a new service offering, we are now providing read-only rsync access against developer CVS. This allows projects to efficiently make on-demand backups of their entire CVS repository. All projects should be making regular backups of their CVS repository contents using this service. 5. Nightly tarball service Nightly tarball service is being dropped in lieu of read-only rsync service. Projects which currently depend on nightly tarballs for repository backups will need to begin using rsync to make a backup copy of their repository contents. We see this as a major functional improvement. For a number of reasons, tarballs have fallen out of sync with the data in the repository at times in the past few years. Tarballs required a substantial amount of additional disk, and I/O to generate. The move to read-only rsync allows backups to be produced on-demand, with an update frequency chosen by the project. 6. Points of failure In the past, developer CVS service for all projects was provided from a single host. CVS pserver service was provided from individual backend heads based on a split of the data. Under our new design, developer CVS and most of our CVS-related services are provided from one of ten CVS hosts (count subject to increase with growth). Each host is independent, and makes a backup copy of the repository data of another host (which is used to provide the pserver CVS service). Failure of a single host will impact only the availability of data on that host. Since the data is split among a larger number of hosts, the size of data impacted by an individual host outage is substantially smaller, and the time required for us to restore service will be substantially shorter. This rapid architecture change has been made possible specifically using the research we performed for our recent launch of Subversion service. We've applied our best practices, produced a substantial amount of internal documentation, and kept an eye toward maintainability. This effort has allowed us to deploy this new architecture quickly once hardware was received, and will permit us to quickly scale this service horizontally as growth and demand requires. Many other minor improvements have also been made to improve the service offering and make it less trouble-prone. The most important of which are listed above. For a full description of the new service offering, and for information on how to use the services described above, please refer to the site documentation for the CVS service after the service has been launched: https://www.sf.net/docs/E04 Thank you, The SourceForge.net Team . |
|
From: Kanacilo, E. <e.m...@tb...> - 2006-04-10 09:15:49
|
Dear Alexander,=20 =20 In previous message, I was referring to the source code.=20 For some DSOL-packages, only the jars are available, but not the source code.=20 A suggestion: for the next releases, keep the version number the same for all dependent packages, like it is DSOL 2.0 and its dependencies dsol-gui 2.0, dsol-xml 2.0 and so on. It is easier when working with the source code.=20 =20 Kind regards, Elisangela=20 ________________________________ From: Alexander Verbraeck [mailto:a.v...@tu...]=20 Sent: Friday, April 07, 2006 8:42 PM To: Kanacilo, Elisangela Cc: dsol-development Subject: RE: missing dsol packages =20 Dear Elisangela, =20 My proposal is as follows: - To make a DSOL version 1.6.7 available that works with MAVEN 1 and Java 1.4 - To make a DSOL version 1.7.0 available that works with MAVEN 2 and Java 1.4 - To make a DSOL version 2.1.0 available that works with MAVEN 2 and Java 5.0 =20 That would probably solve most people's problems that everyone seems to experience right now... I have had many requests for a 'full 1.6.6' version, without it being clearly present at any CVS. I believe that the version that Stijn-Pieter and I are using (called 1.6.6s) would be an excellent candidate for the 1.6.7 and 1.7.0 branches. The most important thing is that we incorporate the same changes in version 2.1.0 (mainly serialization and networking updates). =20 Kind regards, Alexander Verbraeck =20 =20 ________________________________ From: Kanacilo, Elisangela [mailto:e.m...@tb...]=20 Sent: 07 April 2006 18:02 To: Alexander Verbraeck Subject: missing dsol packages =20 Dear Alexander,=20 =20 I was checking previous versions of DSOL and not all the versions of DSOL packages are available, neither in CVS, nor in sk-2 (shadow directory). Some packages suggests version 2.00 but in the correspondent project.xml defines a different version, which might create a confusion about the package version. Here is a list of missing files or inconsistencies in package versions: =20 1- dsol: versions 1.6.4 and 1.6.5 are missing, but I don't think it is a big problem. Unless you want to make all the versions available. 2- dsol-gui: only versions 1.6.0 and root_Release_200 are available. The latest suggests version 2.00, but in the project.xml is written 1.6.3. Version 1.6.0 is an old version which is not even maven compatible. 3- dsol-xml: only versions 1.6.0 and root_release_200 are available. The latest suggests version 2.00, but in the project.xml is written 1.6.3. . Version 1.6.0 is an old version which is not even maven compatible. 4- interpreter: only versions 1.6.0 and root_release_200 are available. The latest suggests version 2.00, but in the project.xml is written 1.6.3. . Version 1.6.0 is an old version which is not even maven compatible. 5- introspection: only versions 1.6.3, 1.6.0 and root_release_200 are available. Version 1.6.0 is an old version which is not even maven compatible. Problems: Version 1.6.3 , project.xml is written 1.6.2=20 6- jstats: missing 1.6.6 7- language: missing 1.6.4, but I don't think it is a big problem 8- logger: 1.6.4 is missing =20 The most urgent I need for the project is=20 Dsol-gui 1.6.6 Dsol-xml 1.6.4 Interpreter 1.6.6 Introspection 1.6.4 Jstat 1.6.6. Logger 1.6.4 =20 When you can upload these versions to CVS or to SK-2, please let me know. Kind regards =20 Elisangela Mieko Kanacilo PhD Candidate Systems Engineering Group Faculty of Technology, Policy and Management Delft University of Technology Address: Jaffalaan, 5, room a2.390 2628BX, Delft, The Netherlands. Phone Number: +31 (15) 278-5446 =20 |
|
From: Alexander V. <a.v...@tu...> - 2006-04-07 18:42:29
|
Dear Elisangela, My proposal is as follows: - To make a DSOL version 1.6.7 available that works with MAVEN 1 and Java 1.4 - To make a DSOL version 1.7.0 available that works with MAVEN 2 and Java 1.4 - To make a DSOL version 2.1.0 available that works with MAVEN 2 and Java 5.0 That would probably solve most people's problems that everyone seems to experience right now... I have had many requests for a 'full 1.6.6' version, without it being clearly present at any CVS. I believe that the version that Stijn-Pieter and I are using (called 1.6.6s) would be an excellent candidate for the 1.6.7 and 1.7.0 branches. The most important thing is that we incorporate the same changes in version 2.1.0 (mainly serialization and networking updates). Kind regards, Alexander Verbraeck _____ From: Kanacilo, Elisangela [mailto:e.m...@tb...] Sent: 07 April 2006 18:02 To: Alexander Verbraeck Subject: missing dsol packages Dear Alexander, I was checking previous versions of DSOL and not all the versions of DSOL packages are available, neither in CVS, nor in sk-2 (shadow directory). Some packages suggests version 2.00 but in the correspondent project.xml defines a different version, which might create a confusion about the package version. Here is a list of missing files or inconsistencies in package versions: 1- dsol: versions 1.6.4 and 1.6.5 are missing, but I don't think it is a big problem. Unless you want to make all the versions available. 2- dsol-gui: only versions 1.6.0 and root_Release_200 are available. The latest suggests version 2.00, but in the project.xml is written 1.6.3. Version 1.6.0 is an old version which is not even maven compatible. 3- dsol-xml: only versions 1.6.0 and root_release_200 are available. The latest suggests version 2.00, but in the project.xml is written 1.6.3. . Version 1.6.0 is an old version which is not even maven compatible. 4- interpreter: only versions 1.6.0 and root_release_200 are available. The latest suggests version 2.00, but in the project.xml is written 1.6.3. . Version 1.6.0 is an old version which is not even maven compatible. 5- introspection: only versions 1.6.3, 1.6.0 and root_release_200 are available. Version 1.6.0 is an old version which is not even maven compatible. Problems: Version 1.6.3 , project.xml is written 1.6.2 6- jstats: missing 1.6.6 7- language: missing 1.6.4, but I don't think it is a big problem 8- logger: 1.6.4 is missing The most urgent I need for the project is Dsol-gui 1.6.6 Dsol-xml 1.6.4 Interpreter 1.6.6 Introspection 1.6.4 Jstat 1.6.6. Logger 1.6.4 When you can upload these versions to CVS or to SK-2, please let me know. Kind regards Elisangela Mieko Kanacilo PhD Candidate Systems Engineering Group Faculty of Technology, Policy and Management Delft University of Technology Address: Jaffalaan, 5, room a2.390 2628BX, Delft, The Netherlands. Phone Number: +31 (15) 278-5446 |
|
From: R.T.H.Chin <r.t...@tb...> - 2006-03-27 12:56:40
|
Dear Alexander,
I went through the book and the code again. Most of my questions are
answered now. This is how it works:
There are actually three types of "events" in DSOL:
(1) the timestep of the Animator,
(2) a discrete time event,
(3) the timestep of a differential equation
The Animator proceeds to its next timestep, or to a discrete time event
within its timestep (whichever comes first). Next the differential
equation(s) are integrated until the current time using the timestep of
DifferentialEquation (in jstats.ode). A ratio is used in
DifferentialEquation.integrateY() to correct the mismatch in the (final)
timestep. Next, if a discrete event is scheduled it is executed by the
Animator. Finally it starts all over again until the simulation is finished.
So that solves the questions 1,2,3, and 5 in my previous mail. One
question remains:
4 What is you have two differential equations which should be solved at
two different timesteps (e.g. a high frequency motion and a low
frequency motion)?
Differential equations are solved as soon as they receive a
TIME_CHANGED_EVENT. However, by my knowledge you cannot know the order
in which different differential equations (instances of
DifferentialEquation) are notified and thus integrated/solved. I assume
that a similar thing probably happens when discrete time events are
scheduled at the same time, but suppose the following:
Suppose I have 2 differential equations EQ1 and EQ2. EQ1 is a low
frequency motion which is solved every 10 seconds. EQ2 is a high
frequency motion which is solved every second. The outcomes of EQ2 are
input for EQ1, and may be assumed to be stable during a 10 second
interval. Suppose the time interval of Animator is set by the user to
25 seconds. Then it does matter in which order the equations are solved,
and the outcome would unpredictable since we don't know what the user
will do in advance. Or should we prevent a user from setting the
Animator time interval in the DSOLapp?
Kind regards,
Roy
Alexander Verbraeck wrote:
>Dear Roy,
>
>The implementation exactly follows the suggested implementation for the
>DEV&DESS formalism as described in B.P. Zeigler, H. Praehofer & T.G. Kim,
>Theory of Modeling and Simulation, 2nd Edition, Academic Press, 2000. In
>section 9.6 (pp. 222-227), the algorithm is described. With a clear reason
>for integrating in-between. Figure 11 on page 221 of Zeigler's book is also
>interesting.
>
>I will post a separate document on the DSOL website on the implementation of
>the DEV&DESS simulator later, as this often leads to questions and
>confusion.
>
>There is, by the way, one small mistake in the implementation of the
>Animator that extends the DEVDESSSimulator, which relates to the
>implementation of the start() and stop() methods. This will be corrected in
>the next version of DSOL.
>
>Kind regards,
>Alexander Verbraeck
>
>
>
>>-----Original Message-----
>>From: dso...@li... [mailto:dsol-
>>dev...@li...] On Behalf Of R.T.H.Chin
>>Sent: 27 March 2006 11:01
>>To: dso...@li...
>>Subject: [Dsol-development] Confused about DESS implementation
>>
>>Hi DSOL team,
>>
>>Not that I need it right now, actually I don't even use it and should
>>focus on other stuff right now, but studying the DSOL code I'm kind of
>>confused about the DESS implementation.
>>
>>Suppose I use the DSOL application, so then I am actually using the
>>Animator as a delayed DEVSDESS simulator. Looking at the code of the
>>Animator I see two nested loops in the run() method:
>>
>>1-the outer loop which just keeps going for as long as the simulation is
>>not finished
>>2-the inner loop which runs until simulatorTime + timeStep
>>
>>The loop 2 handles all DEVS-events (event.execute() ). Every time such
>>an event is executed a TIME_CHANGED_EVENT is fired. After loop 2 another
>>TIME_CHANGED_EVENT is fired.
>>
>>Suppose my model uses both discrete events and differential equations.
>>Alse suppose that for a specific timestep four events were executed,
>>then 4+1=5 TIME_CHANGED_EVENTS are fired in loop 2.
>>
>>The class
>>nl.tudelft.simulation.dsol.formalisms.dess.DifferentialEquation is a
>>listener and listens to TIME_CHANGED_EVENTs in the notify() method. A
>>differential equation is solved every time a TIME_CHANGED_EVENT is
>>fired. So in my example that means that the differential equation is
>>solved 5 times:
>>
>>public synchronized void notify(final EventInterface event) {
>> ...
>> this.previousY = integrateY(this.simulator.getSimulatorTime(),
>> this.previousX, this.previousY);
>> ...
>> this.previousX = this.simulator.getSimulatorTime();
>>}
>>
>>This is kind of confusing because:
>>1 Shouldn't a differential equation only be solved at specified timeSteps?
>>2 The constructor of DifferentialEquation allows setting a timeStep, but
>>what is the use of that if the equations are solved at
>>TIME_CHANGED_EVENTS?
>>3 What if you set a timestep of DifferentialEquation in the constructor
>>which differs from the timeStep in Animator: are the results still
>>correct?
>>4 What is you have two differential equations which should be solved at
>>two different timesteps (e.g. a high frequency motion and a low
>>frequency motion)?
>>5 What if you use variable timestep algorithms to optimize the timestep
>>/ minimize the error?
>>
>>Maybe I didn't understand the code, and I didn't make a test, but it
>>seems kind of odd.
>>Greetings,
>>Roy
>>
>>
>>-------------------------------------------------------
>>This SF.Net email is sponsored by xPML, a groundbreaking scripting
>>language
>>that extends applications into web and mobile media. Attend the live
>>webcast
>>and join the prime developer group breaking into this new coding
>>territory!
>>http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642
>>_______________________________________________
>>Dsol-development mailing list
>>Dso...@li...
>>https://lists.sourceforge.net/lists/listinfo/dsol-development
>>
>>
>
>
>
>
|
|
From: Alexander V. <a.v...@tu...> - 2006-03-27 09:13:12
|
Dear Roy,
The implementation exactly follows the suggested implementation for the
DEV&DESS formalism as described in B.P. Zeigler, H. Praehofer & T.G. Kim,
Theory of Modeling and Simulation, 2nd Edition, Academic Press, 2000. In
section 9.6 (pp. 222-227), the algorithm is described. With a clear reason
for integrating in-between. Figure 11 on page 221 of Zeigler's book is also
interesting.
I will post a separate document on the DSOL website on the implementation of
the DEV&DESS simulator later, as this often leads to questions and
confusion.
There is, by the way, one small mistake in the implementation of the
Animator that extends the DEVDESSSimulator, which relates to the
implementation of the start() and stop() methods. This will be corrected in
the next version of DSOL.
Kind regards,
Alexander Verbraeck
> -----Original Message-----
> From: dso...@li... [mailto:dsol-
> dev...@li...] On Behalf Of R.T.H.Chin
> Sent: 27 March 2006 11:01
> To: dso...@li...
> Subject: [Dsol-development] Confused about DESS implementation
>
> Hi DSOL team,
>
> Not that I need it right now, actually I don't even use it and should
> focus on other stuff right now, but studying the DSOL code I'm kind of
> confused about the DESS implementation.
>
> Suppose I use the DSOL application, so then I am actually using the
> Animator as a delayed DEVSDESS simulator. Looking at the code of the
> Animator I see two nested loops in the run() method:
>
> 1-the outer loop which just keeps going for as long as the simulation is
> not finished
> 2-the inner loop which runs until simulatorTime + timeStep
>
> The loop 2 handles all DEVS-events (event.execute() ). Every time such
> an event is executed a TIME_CHANGED_EVENT is fired. After loop 2 another
> TIME_CHANGED_EVENT is fired.
>
> Suppose my model uses both discrete events and differential equations.
> Alse suppose that for a specific timestep four events were executed,
> then 4+1=5 TIME_CHANGED_EVENTS are fired in loop 2.
>
> The class
> nl.tudelft.simulation.dsol.formalisms.dess.DifferentialEquation is a
> listener and listens to TIME_CHANGED_EVENTs in the notify() method. A
> differential equation is solved every time a TIME_CHANGED_EVENT is
> fired. So in my example that means that the differential equation is
> solved 5 times:
>
> public synchronized void notify(final EventInterface event) {
> ...
> this.previousY = integrateY(this.simulator.getSimulatorTime(),
> this.previousX, this.previousY);
> ...
> this.previousX = this.simulator.getSimulatorTime();
> }
>
> This is kind of confusing because:
> 1 Shouldn't a differential equation only be solved at specified timeSteps?
> 2 The constructor of DifferentialEquation allows setting a timeStep, but
> what is the use of that if the equations are solved at
> TIME_CHANGED_EVENTS?
> 3 What if you set a timestep of DifferentialEquation in the constructor
> which differs from the timeStep in Animator: are the results still
> correct?
> 4 What is you have two differential equations which should be solved at
> two different timesteps (e.g. a high frequency motion and a low
> frequency motion)?
> 5 What if you use variable timestep algorithms to optimize the timestep
> / minimize the error?
>
> Maybe I didn't understand the code, and I didn't make a test, but it
> seems kind of odd.
> Greetings,
> Roy
>
>
> -------------------------------------------------------
> This SF.Net email is sponsored by xPML, a groundbreaking scripting
> language
> that extends applications into web and mobile media. Attend the live
> webcast
> and join the prime developer group breaking into this new coding
> territory!
> http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642
> _______________________________________________
> Dsol-development mailing list
> Dso...@li...
> https://lists.sourceforge.net/lists/listinfo/dsol-development
|
|
From: R.T.H.Chin <r.t...@tb...> - 2006-03-27 09:01:34
|
Hi DSOL team,
Not that I need it right now, actually I don't even use it and should
focus on other stuff right now, but studying the DSOL code I'm kind of
confused about the DESS implementation.
Suppose I use the DSOL application, so then I am actually using the
Animator as a delayed DEVSDESS simulator. Looking at the code of the
Animator I see two nested loops in the run() method:
1-the outer loop which just keeps going for as long as the simulation is
not finished
2-the inner loop which runs until simulatorTime + timeStep
The loop 2 handles all DEVS-events (event.execute() ). Every time such
an event is executed a TIME_CHANGED_EVENT is fired. After loop 2 another
TIME_CHANGED_EVENT is fired.
Suppose my model uses both discrete events and differential equations.
Alse suppose that for a specific timestep four events were executed,
then 4+1=5 TIME_CHANGED_EVENTS are fired in loop 2.
The class
nl.tudelft.simulation.dsol.formalisms.dess.DifferentialEquation is a
listener and listens to TIME_CHANGED_EVENTs in the notify() method. A
differential equation is solved every time a TIME_CHANGED_EVENT is
fired. So in my example that means that the differential equation is
solved 5 times:
public synchronized void notify(final EventInterface event) {
...
this.previousY = integrateY(this.simulator.getSimulatorTime(),
this.previousX, this.previousY);
...
this.previousX = this.simulator.getSimulatorTime();
}
This is kind of confusing because:
1 Shouldn't a differential equation only be solved at specified timeSteps?
2 The constructor of DifferentialEquation allows setting a timeStep, but
what is the use of that if the equations are solved at TIME_CHANGED_EVENTS?
3 What if you set a timestep of DifferentialEquation in the constructor
which differs from the timeStep in Animator: are the results still correct?
4 What is you have two differential equations which should be solved at
two different timesteps (e.g. a high frequency motion and a low
frequency motion)?
5 What if you use variable timestep algorithms to optimize the timestep
/ minimize the error?
Maybe I didn't understand the code, and I didn't make a test, but it
seems kind of odd.
Greetings,
Roy
|
|
From: Alexander V. <a.v...@tu...> - 2006-03-19 05:27:56
|
Dear Francisco, a) No, but this is very easy to create. Make a class that extends the XYChart class in the DSOL package and override the notify method, or create class that is based on the XYChart class from the jstats project, and create your own notify method (also see XYSeries, which is an interesting class). Just measuring data can done very easily with any class that implements an EventListenerInterface. You could even subscribe it to the TIME_CHANGED_EVENT of your simulator to poll the value(s) you are intersted in, or using a more intelligent event that notifies the state changes you are interested in. b) No, but it is as easy te create as the above class. c) Not yet -- it is not so difficult to make, and there are a few public domain classes that you could incorporate in DSOL, or write it yourself. This could be a nice contribution to the dsol project. I copied the dsol development list on the e-mail, as there might be someone who already created more extensive statisctics packages (Niels?). Kind regards, Alexander. > -----Original Message----- > From: Francisco Hederra [mailto:fhe...@is...] > Sent: 16 March 2006 21:38 > To: Alexander Verbraeck > Cc: chr...@is... > Subject: DSOL Stat Classes > > Hello Doctor Verbraeck, > > I have been running experiments with multiple replications using DSOL > (1.6.6) and I have some questions regarding DSOL Classes: > > a) Does DSOL provide a Stat class that saves the sample paths (either in > memory or the capabiltity to write to a file)? > b) Does DSOL provide a Stat class that can collect samples in all > replications of a single treatment? > c) Is there a class in DSOL that can be used to do Batch-Means analysis? > > > > Thank you, > Francisco Hederra > Ph.D Student > Georgia Institue of Technology. > > > > > |
|
From: Alexander V. <a.v...@tu...> - 2006-02-11 09:45:25
|
RGVhciBGcmFuc2lzY28sDQoNCkkgd2lsbCB0YWtlIGEgbG9vay4gSSBhbSBzdGlsbCB3b3JraW5n IHdpdGggdmVyc2lvbiAxLjYuNiBteXNlbGYgLS0gdGhlIDIuMCB2ZXJzaW9uIHRoYXQgaXMgcHJl cGFyZWQgZm9yIEphdmEgMS41IGlzIHN0aWxsIHVuZGVyZ29pbmcgdGVzdGluZywgYW5kIEkgYW0g d29ya2luZyBvbiB0aGUgY2hhbmdlIHJlcG9ydCBhbmQgdGhlIGRvY3VtZW50YXRpb24gZm9yIDIu MC4gRXNwZWNpYWxseSB0aGUgd2F5IHlvdSB3b3JrIHdpdGggZXhwZXJpbWVudHMgYW5kIHRyZWF0 bWVudHMgaGFzIGNoYW5nZWQuDQoNCktpbmQgcmVnYXJkcywNCkFsZXhhbmRlciBWZXJicmFlY2sN Cg0KPiAtLS0tLU9yaWdpbmFsIE1lc3NhZ2UtLS0tLQ0KPiBGcm9tOiBGcmFuY2lzY28gSGVkZXJy YSBbbWFpbHRvOmZoZWRlcnJhQGlzeWUuZ2F0ZWNoLmVkdV0NCj4gU2VudDogRnJpZGF5LCAxMCBG ZWJydWFyeSAyMDA2IDIwOjQ2DQo+IFRvOiAnQWxleGFuZGVyIFZlcmJyYWVjaycNCj4gU3ViamVj dDogRFNPTCBjb21waWxhdGlvbg0KPiANCj4gDQo+IEhpIGRvY3RvciBWZXJicmFlY2ssDQo+IA0K PiBJIGp1c3QgZG93bmxvYWRlZCB0aGUgbGF0ZXN0IHByb2plY3QgdmVyc2lvbnMgKEhFQUQpIGZy b20gdGhlIA0KPiBDVlMgdXNpbmcNCj4gRWNsaXBzZS4NCj4gDQo+IFRoZXkgZG9uJ3QgaGF2ZSBt YXZlbiBmaWxlcyBhbnltb3JlLg0KPiBIb3cgc2hvdWxkIEkgY29tcGlsZSB0aGUgZGlmZmVyZW50 IHByb2plY3RzIGFuZCBkc29sIGFzIGEgDQo+IHdob2xlIHByb2plY3Q/DQo+IA0KPiANCj4gVGhh bmsgeW91LA0KPiANCj4gRnJhbmNpc2NvIEhlZGVycmENCj4gUGguRCBTdHVkZW50DQo+IEdlb3Jn YSBJbnN0aXR1ZSBvZiBUZWNobm9sb2d5Lg0KPiAgDQo+IA== |
|
From: Bastiaan v. de R. <in...@ra...> - 2005-04-09 11:44:58
|
Bennie,
Fix it --> just make the different EventTypes static.
Like:
/*
* Created on 9-apr-2005
* File name EventProducerExtension.java
*
* Created by B.J.A van de Rakt M.Sc.
* Copyright (c) 2004 INITI8
/**
* @author Rakt
*/
public class EventProducerExtension extends EventProducer
{
private static int counter = 1;
private static EventType eventTypeA = new EventType("A");
private static EventType eventTypeB = new EventType("B");
private static EventType eventTypeC = new EventType("C");
//etc...
public EventProducerExtension()
{
super();
EventProducerExtension.eventTypeA = new EventType("A" + counter);
EventProducerExtension.eventTypeB = new EventType("B" + counter);
EventProducerExtension.eventTypeB = new EventType("C" + counter);
System.out.println(EventProducerExtension.eventTypeA.toString());
System.out.println(EventProducerExtension.eventTypeB.toString());
System.out.println(EventProducerExtension.eventTypeC.toString());
counter++;
}
public static void main(String[] args)
{
for (int i=0;i<10;i++){
new EventProducerExtension();}
//new EventProducerExtension();
}
}
kind regards,
Bastiaan
Bennie Talma wrote:
> Hi all,
>
> I'm getting an error when trying to define more than one EventType in
> a class. There is no problem when I only define either one of the two
> EventTypes on its own. The DSOL java doc explains that the values of
> the EventTypes should be unique, as I've done in my example. I have
> included the exception message and code of the class.
>
> Does anyone know what causes this problem and how to fix it?
>
> Thanks,
> Bennie
>
>
> Exception in thread "main" java.lang.NullPointerException
> at
> nl.tudelft.simulation.event.EventProducer.checkEventType(EventProducer.java:80)
> at
> nl.tudelft.simulation.event.EventProducer.<init>(EventProducer.java:95)
> at
> nl.tudelft.simulation.test.EventProducerExtension.<init>(EventProducerExtension.java:22)
> at
> nl.tudelft.simulation.test.EventProducerExtension.main(EventProducerExtension.java:30)
>
>
> public class EventProducerExtension extends EventProducer
> {
>
> private static int counter = 1;
> private EventType eventTypeA = new EventType("A");
> private EventType eventTypeB = new EventType("B");
>
> public EventProducerExtension()
> {
> super();
> this.eventTypeA = new EventType("A" + counter);
> this.eventTypeB = new EventType("B " + counter);
> counter++;
> }
>
> public static void main(String[] args)
> {
> new EventProducerExtension();
> new EventProducerExtension();
> }
>
> }
>
|
|
From: Bennie T. <B.J...@st...> - 2005-04-09 07:49:05
|
Hi all,
I'm getting an error when trying to define more than one EventType in a
class. There is no problem when I only define either one of the two
EventTypes on its own. The DSOL java doc explains that the values of the
EventTypes should be unique, as I've done in my example. I have included the
exception message and code of the class.
Does anyone know what causes this problem and how to fix it?
Thanks,
Bennie
Exception in thread "main" java.lang.NullPointerException
at
nl.tudelft.simulation.event.EventProducer.checkEventType(EventProducer.java:
80)
at
nl.tudelft.simulation.event.EventProducer.<init>(EventProducer.java:95)
at
nl.tudelft.simulation.test.EventProducerExtension.<init>(EventProducerExtens
ion.java:22)
at
nl.tudelft.simulation.test.EventProducerExtension.main(EventProducerExtensio
n.java:30)
public class EventProducerExtension extends EventProducer
{
private static int counter = 1;
private EventType eventTypeA = new EventType("A");
private EventType eventTypeB = new EventType("B");
public EventProducerExtension()
{
super();
this.eventTypeA = new EventType("A" + counter);
this.eventTypeB = new EventType("B " + counter);
counter++;
}
public static void main(String[] args)
{
new EventProducerExtension();
new EventProducerExtension();
}
}
|
|
From: R.T.H.Chin <r.t...@tb...> - 2005-03-14 07:56:17
|
Hi DSOL fans, I made a tutorial on how to install DSOL from CVS. You can find it on my personal website (for now) at: http://www.tbm.tudelft.nl/webstaf/Royc/tutorials/Checking_out_DSOL_from_CVS.pdf Hope you like it. If you find any errors then please let me know. Greetings, Roy |
|
From: Peter H.M. J. <p.h...@tb...> - 2005-03-12 16:25:38
|
Roy, go the dsol-gui, the dsol-tutorial dir en type maven eclipse-all success! Peter R.T.H.Chin wrote: > Anyway, I found that maven eclipse-all solves most problems; no need > for dist-all. > Still dsol_gui and dsol_tutorial give errors: > > Project dsol-gui is missing required library: 'C:Documents and > Settings/royc/.maven/repository/dsol/jars/interpreter-1.6.8.jar' > Project dsol-tutorial is missing required library: 'C:Documents and > Settings/royc/.maven/repository/dsol/jars/dsol-full-1.6.3.jar' > Project dsol-tutorial is missing required source folder: 'src/test' > > How do I solve that? > Roy > > > > Chin, Roy wrote: > >> Hi Peter, >> >> I'm trying to install the latest DSOL from cvs for almost 2 hours >> now. I did a "maven build-all" from the dsol project. >> It just keeps hanging on lines such as: >> >> Checking link http://www.tbm.tudelft.nl/webstaf/peterja >> >> or other links in this domain. Only after waiting for a very very >> long time it continues, until it finds another "webstaf" site. >> >> ow and now it finally continues ... with this result: >> BUILD FAILED >> File...... c:\Eclipse_workspaces\Eclipse3\dsol116\dsol\maven.xml >> Element... maven:reactor >> Line...... 6 >> Column.... 61 >> Unable to obtain goal [dist:deploy-bin] -- C:\Documents and >> Settings\royc\.maven\cache\maven-artifact-plugin-1.4\plugin.jelly:94:13: >> <artifact:artifact-deploy> Unable to deploy to any repositories >> Total time: 17 minutes 56 seconds >> Finished at: Sat Mar 12 15:35:09 CET 2005 >> >> >> There is really no end to it ... what's happening? >> I just want to play with DSOL! :( >> >> Roy >> >> B.t.w. I tried to post my 3D tutorial to the DSOL mailing list, but >> it's still not there. >> > > > > > ------------------------------------------------------- > SF email is sponsored by - The IT Product Guide > Read honest & candid reviews on hundreds of IT Products from real users. > Discover which products truly live up to the hype. Start reading now. > http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click > _______________________________________________ > Dsol-development mailing list > Dso...@li... > https://lists.sourceforge.net/lists/listinfo/dsol-development |
|
From: R.T.H.Chin <r.t...@tb...> - 2005-03-12 16:23:34
|
Anyway, I found that maven eclipse-all solves most problems; no need for dist-all. Still dsol_gui and dsol_tutorial give errors: Project dsol-gui is missing required library: 'C:Documents and Settings/royc/.maven/repository/dsol/jars/interpreter-1.6.8.jar' Project dsol-tutorial is missing required library: 'C:Documents and Settings/royc/.maven/repository/dsol/jars/dsol-full-1.6.3.jar' Project dsol-tutorial is missing required source folder: 'src/test' How do I solve that? Roy Chin, Roy wrote: > Hi Peter, > > I'm trying to install the latest DSOL from cvs for almost 2 hours now. > I did a "maven build-all" from the dsol project. > It just keeps hanging on lines such as: > > Checking link http://www.tbm.tudelft.nl/webstaf/peterja > > or other links in this domain. Only after waiting for a very very long > time it continues, until it finds another "webstaf" site. > > ow and now it finally continues ... with this result: > BUILD FAILED > File...... c:\Eclipse_workspaces\Eclipse3\dsol116\dsol\maven.xml > Element... maven:reactor > Line...... 6 > Column.... 61 > Unable to obtain goal [dist:deploy-bin] -- C:\Documents and > Settings\royc\.maven\cache\maven-artifact-plugin-1.4\plugin.jelly:94:13: > <artifact:artifact-deploy> Unable to deploy to any repositories > Total time: 17 minutes 56 seconds > Finished at: Sat Mar 12 15:35:09 CET 2005 > > > There is really no end to it ... what's happening? > I just want to play with DSOL! :( > > Roy > > B.t.w. I tried to post my 3D tutorial to the DSOL mailing list, but > it's still not there. > |
|
From: R.T.H.Chin <r.t...@tb...> - 2005-03-12 15:02:56
|
Hi DSOL fans, Here's a new tutorial for 3D animation in DSOL: http://www.tbm.tudelft.nl/webstaf/royc/dsol_aquarium/index.html Currently it's still on my personal site, but there are plans to move it to the official DSOL site later on. Greetings, Roy P.S Also posted this yesterday, but it didn't appear ... |
|
From: Chin, R. <r.t...@tb...> - 2005-03-12 14:37:41
|
Hi Peter, I'm trying to install the latest DSOL from cvs for almost 2 hours now. I = did a "maven build-all" from the dsol project. It just keeps hanging on lines such as: Checking link http://www.tbm.tudelft.nl/webstaf/peterja or other links in this domain. Only after waiting for a very very long = time it continues, until it finds another "webstaf" site. ow and now it finally continues ... with this result: BUILD FAILED File...... c:\Eclipse_workspaces\Eclipse3\dsol116\dsol\maven.xml Element... maven:reactor Line...... 6 Column.... 61 Unable to obtain goal [dist:deploy-bin] -- C:\Documents and = Settings\royc\.maven\cache\maven-artifact-plugin-1.4\plugin.jelly:94:13: = <artifact:artifact-deploy> Unable to deploy to any repositories Total time: 17 minutes 56 seconds Finished at: Sat Mar 12 15:35:09 CET 2005 There is really no end to it ... what's happening? I just want to play with DSOL! :( Roy B.t.w. I tried to post my 3D tutorial to the DSOL mailing list, but it's = still not there. |
|
From: Houten, Stijn-P. v. <s.p...@tb...> - 2005-03-09 20:49:04
|
Hi Benny,
=20
* How can I determine the year, month, day, hour, minute and second from
the long value that is returned by Treatment.getStartTime()?
The long value is expressed in milliseconds, though I am not sure about
this. However, as soon as you make sure this long value is expressed in
milliseconds you can use the java.util.Calendar object for what you
want. Lookup the java doc for the specs, but it does support you in all
your needs.=20
=20
=20
* Is it possible to set the size of the DSOL main window so that I don't
have to resize it every time I run the application?
Unfortunately, this size is set as a finel in the DSOLFrame of the
DSOL-GUI class. My best guess is to build your own frame which
implements the DSOLApplicationInterface. Than you will be able to do
whatever you want.
=20
/** the preferredSize is the preferredSize of the panel */
public static final Dimension PREFERRED_SIZE =3D new
Dimension(400, 375);
=20
=20
* In Eclipse, when running an application in debug mode, is it
possible to specify a condition that will result in a break. For
example, I want the debugger to break when a variable reaches a certain
value and not at a breakpoint.
=20
I am not sure, however, you can also think of a work around (e.g. an
if-statement). Whenever your value is reached, you enter the
if-statement, in which you place your breakpoint.
=20
Hope this helps,
=20
Best regards,
=20
Stijn-Pieter van Houten.
=20
=20
=20
________________________________
Van: dso...@li...
[mailto:dso...@li...] Namens Bennie
Talma
Verzonden: woensdag 9 maart 2005 21:32
Aan: dso...@li...
Onderwerp: [Dsol-development] Time, size and debug
=20
Hi all,
I have some questions and I hope someone can help me out:
* How can I determine the year, month, day, hour, minute and second from
the long value that is returned by Treatment.getStartTime()?
* Is it possible to set the size of the DSOL main window so that I don't
have to resize it every time I run the application?
* In Eclipse, when running an application in debug mode, is it possible
to specify a condition that will result in a break. For example, I want
the debugger to break when a variable reaches a certain value and not at
a breakpoint.
Thanks,
Bennie
|
|
From: Bennie T. <B.J...@st...> - 2005-03-09 20:33:37
|
Hi all, I have some questions and I hope someone can help me out: * How can I determine the year, month, day, hour, minute and second from the long value that is returned by Treatment.getStartTime()? * Is it possible to set the size of the DSOL main window so that I don't have to resize it every time I run the application? * In Eclipse, when running an application in debug mode, is it possible to specify a condition that will result in a break. For example, I want the debugger to break when a variable reaches a certain value and not at a breakpoint. Thanks, Bennie |
|
From: Simon M. <msa...@gm...> - 2005-02-21 17:37:43
|
Dear DSOL supporters, I'm planning to use DSOL for developing simulation model for simulating performance of different organizations. Definitely, because performance with time is continuous process and my aim of forecasting the performance using current and preveious scenarios, continuous simulation seems to be more suitable. I had already worked with discrete part of DSOL. But I had never work with continuous simulation using DSOL. I tried to use the DSOL documentation (Masterind D-SOL by Peter Jacobs & Alexander Verbraeck) but the document had only one example for continuous and it seems that it is not complete. Please, I kindly request you to provide me with more documents and example of how a continuous simulation model can be developed using DSOL. Thank you very much, Simon. -- ir. Msanjila, S. S. Institute of informatics University of Amsterdam. www.science.uva.nl/~msanjila |
|
From: Akkermans, J.C.J.M <J.C...@ST...> - 2004-12-17 17:37:19
|
I'm afraid that version 1.6.6. is the reason that my tallies don't work anymore. The same situation is the case with the group of comparison 6. With the old version the tallies do work. Joep -----Original Message----- From: Peter H.M. Jacobs To: 'Dsol-java (E-mail)'; dso...@li... Sent: 12/17/2004 1:35 PM Subject: [Dsol-java] 1.6.6 version Hi all, Due to problems while uploading the 1.6.5. version to sourceforge, I have uploaded a new version 1.6.6. This solved the zip error Bastian mentioned. Peter |
|
From: Peter H.M. J. <p.h...@tb...> - 2004-12-17 12:35:40
|
Hi all, Due to problems while uploading the 1.6.5. version to sourceforge, I have uploaded a new version 1.6.6. This solved the zip error Bastian mentioned. Peter |
|
From: Bastiaan v. de R. <in...@ra...> - 2004-12-17 10:09:14
|
Hi all,
When I add this new release to my projects (and I add the 1.6.2. src
file) and run the DSOL application.class I recieve an error: "fatal
exception occured. program will exit". It gives back the following problems:
java.lang.ExceptionInInitializerError
at
nl.tudelft.simulation.dsol.gui.DSOLApplication.<init>(DSOLApplication.java:70)
at
nl.tudelft.simulation.dsol.gui.DSOLApplication.main(DSOLApplication.java:156)
Caused by: java.lang.NullPointerException
at
nl.tudelft.simulation.dsol.gui.windows.DSOLFrame.<clinit>(DSOLFrame.java:81)
... 2 more
Exception in thread "main"
What did I do wrong?
Kind regards.
Bastiaan van de Rakt.
Peter H.M. Jacobs wrote:
> Hi all,
>
>
>
> I have just uploaded a new *minor* dsol release which contains some
> extra features but mostly fixes a number of bugs
>
>
>
> Please download
> http://prdownloads.sourceforge.net/dsol/dsol-full-1.6.5.jar?download
>
>
>
> Changes include:
>
> · License information has changed in code from GPL to LGPL.
>
> · Model serializability bug fixes.
>
> · DSOL-GUI navigation is xml-based.
>
> · Serious performance upgrade in process interaction
> formalism. Test show that 2,000,000 processes were concurrently
> simulated within 20sec.
>
> · Bugfixes in discrete emprical distribution, resource
> utilization, process interaction synchronization
>
> · Latest RFEs are included.
>
>
>
> Plan for the 1.70 version:
>
> · Experimentation will change. Steady state will be added
>
> · Fuzzy library will be added (currently under review)
>
>
>
> Peter
>
|
