From blaise at idistro.com Sun Dec 3 03:11:39 2006 From: blaise at idistro.com (blaise@idistro.com) Date: Sun, 3 Dec 2006 00:11:39 -0800 (PST) Subject: Building Cougaar from source. In-Reply-To: <200601171027.46606.twright@bbn.com> References: <841721380601122313n3d27013dt@mail.gmail.com> <200601161202.58889.twright@bbn.com> <200601171027.46606.twright@bbn.com> Message-ID: <58355.127.0.0.1.1165133499.squirrel@www.idistro.com> Hello, I've got a few questions about checking out and building cougaar projects from cvs. I've just checked out the source tree using the cvs commands of form: 'cvs -d :pserver:anonymous at cougaar.org:/cvsroot/acme checkout acme' for each project. Is this checking out the source from the current active dev branch, or should I be using the B12_1_5 branch if so how do I do this I tried the -r B12_1_5 tag but it didn't seem to work. Also can't get the source that I have to build, you'll have to excuse my ignorance I'm used to just typing ant or mvn and having everything work itself out from there. I had to take a top level build.xml file (that lives under $COUGAAR_INSTALL_PATH) from one of the zipped distributions, as I couldn't see how to get it out of cvs. I set the env variables COUGAAR_INSTALL_PATH, and JAVA_HOME and typed 'ant'. The build couldn't find classes in the tools.jar to link to. In addition it falls over as java 1.4 is set in the build.xml files and some of the source files contain java 1.5 key words. Also the 3rd party jars aren't found, they are under jars/lib but the build doesn't copy them to sys. Is there a how to guide somewhere on the web site that will take me through the build step by step... Thanks, Blaise. From ahelsing at bbn.com Mon Dec 4 09:02:33 2006 From: ahelsing at bbn.com (Aaron Helsinger) Date: Mon, 04 Dec 2006 09:02:33 -0500 Subject: Building Cougaar from source. In-Reply-To: <58355.127.0.0.1.1165133499.squirrel@www.idistro.com> References: <841721380601122313n3d27013dt@mail.gmail.com> <200601161202.58889.twright@bbn.com> <200601171027.46606.twright@bbn.com> <58355.127.0.0.1.1165133499.squirrel@www.idistro.com> Message-ID: <45742A79.2070007@bbn.com> The -r B12_1_5 arg is correct, but of course, it will only work if there actually is such a branch. The acme module does not have that branch. You can browse which tags are relevant when you use the web based CVS browser. These are standard CVS commands, and a web search should turn up some decent manuals. So the command that you gave checks ou the default branch of the acme module, HEAD. The build.xml files that come out of an individual project (/build.xml) are preset with module specific variables. Use the cougaar-src.zip zip file to get current build.xml files, including a parent level build.xml (to go in COUGAAR_INSTALL_PATH/build.xml) --- these files are in fact regenerated at every build with the current library dependencies, etc. Note however that this archive also includes all the source files, which you may not want. The (Perl) build script is in the build module: build/bin/build and uses the build/data/moduleTemplate.xml file to generate the per module build.xml, and productTemplate.xml to generate the parent level build.xml If you read the comments in the build.xml, they describe what they expect. In particular: The (correct) parent.xml will copy jars/lib into sys as necessary The build module installs its products in /clib so you wont get missing jars there. Basically, you should only need to: 1) Set JAVA_HOME and COUGAAR_INSTALL_PATH 2) checkout the modules under COUGAAR_INSTALL_PATH --- build is the main module for building other libraries, so you'll need that --- bootstrap, javaiopatch, core, util, and base get used by basically everything else, so you'll likely want those Any module that you dont want to build yourself, you can just get it from a recent build. Not all projects/modules on cougaar.org are built using this build process and conform to these conventions. The particular modules that these Ant build scripts know how to build are those that are configured in build/data/default.build. Note however that this data file is extensable, and you could add your own project there (as long as your directory structure conforms. I hope this helps, Aaron blaise at idistro.com wrote: > Hello, > > I've got a few questions about checking out and building cougaar projects > from cvs. I've just checked out the source tree using the cvs commands of > form: 'cvs -d :pserver:anonymous at cougaar.org:/cvsroot/acme checkout acme' > for each project. Is this checking out the source from the current active > dev branch, or should I be using the B12_1_5 branch if so how do I do this > I tried the -r B12_1_5 tag but it didn't seem to work. > > Also can't get the source that I have to build, you'll have to excuse my > ignorance I'm used to just typing ant or mvn and having everything work > itself out from there. I had to take a top level build.xml file (that > lives under $COUGAAR_INSTALL_PATH) from one of the zipped distributions, > as I couldn't see how to get it out of cvs. I set the env variables > COUGAAR_INSTALL_PATH, and JAVA_HOME and typed 'ant'. The build couldn't > find classes in the tools.jar to link to. In addition it falls over as > java 1.4 is set in the build.xml files and some of the source files > contain java 1.5 key words. Also the 3rd party jars aren't found, they are > under jars/lib but the build doesn't copy them to sys. Is there a how to > guide somewhere on the web site that will take me through the build step > by step... > > Thanks, > > Blaise. > _______________________________________________ > Cougaar-developers mailing list > Cougaar-developers at cougaar.org > http://cougaar.org/mailman/listinfo/cougaar-developers > > > From twright at bbn.com Mon Dec 4 20:33:50 2006 From: twright at bbn.com (Todd Wright) Date: Mon, 04 Dec 2006 20:33:50 -0500 Subject: Building Cougaar from source. In-Reply-To: <45742A79.2070007@bbn.com> References: <841721380601122313n3d27013dt@mail.gmail.com> <200601161202.58889.twright@bbn.com> <200601171027.46606.twright@bbn.com> <58355.127.0.0.1.1165133499.squirrel@www.idistro.com> <45742A79.2070007@bbn.com> Message-ID: <4574CC7E.50103@bbn.com> As Aaron notes, the easiest option is to download a recent build and use the top-level "build.xml" in the "cougaar-src.zip": ant install However, I just tried this and found several bugs. Attached below are my notes and workarounds. The Perl script is fairly complex and difficult to use. I'd avoid it if possible. Todd Aaron Helsinger wrote: > The -r B12_1_5 arg is correct, but of course, it will only work if there > actually is such a branch. The acme module does not have that branch. > You can browse which tags are relevant when you use the web based CVS > browser. > > These are standard CVS commands, and a web search should turn up some > decent manuals. > > So the command that you gave checks ou the default branch of the acme > module, HEAD. > > The build.xml files that come out of an individual project > (/build.xml) are preset with module specific variables. > > Use the cougaar-src.zip zip file to get current build.xml files, > including a parent level build.xml (to go in > COUGAAR_INSTALL_PATH/build.xml) --- these files are in fact regenerated > at every build with the current library dependencies, etc. Note however > that this archive also includes all the source files, which you may not > want. > > The (Perl) build script is in the build module: build/bin/build and uses > the build/data/moduleTemplate.xml file to generate the per module > build.xml, and productTemplate.xml to generate the parent level build.xml > > If you read the comments in the build.xml, they describe what they expect. > In particular: > The (correct) parent.xml will copy jars/lib into sys as necessary > The build module installs its products in /clib so you wont get missing > jars there. > > Basically, you should only need to: > 1) Set JAVA_HOME and COUGAAR_INSTALL_PATH > 2) checkout the modules under COUGAAR_INSTALL_PATH > --- build is the main module for building other libraries, so you'll > need that > --- bootstrap, javaiopatch, core, util, and base get used by basically > everything else, so you'll likely want those > > Any module that you dont want to build yourself, you can just get it > from a recent build. > Not all projects/modules on cougaar.org are built using this build > process and conform to these conventions. The particular modules that > these Ant build scripts know how to build are those that are configured > in build/data/default.build. Note however that this data file is > extensable, and you could add your own project there (as long as your > directory structure conforms. > > I hope this helps, > > Aaron > > blaise at idistro.com wrote: > >>Hello, >> >>I've got a few questions about checking out and building cougaar projects >>from cvs. I've just checked out the source tree using the cvs commands of >>form: 'cvs -d :pserver:anonymous at cougaar.org:/cvsroot/acme checkout acme' >>for each project. Is this checking out the source from the current active >>dev branch, or should I be using the B12_1_5 branch if so how do I do this >>I tried the -r B12_1_5 tag but it didn't seem to work. >> >>Also can't get the source that I have to build, you'll have to excuse my >>ignorance I'm used to just typing ant or mvn and having everything work >>itself out from there. I had to take a top level build.xml file (that >>lives under $COUGAAR_INSTALL_PATH) from one of the zipped distributions, >>as I couldn't see how to get it out of cvs. I set the env variables >>COUGAAR_INSTALL_PATH, and JAVA_HOME and typed 'ant'. The build couldn't >>find classes in the tools.jar to link to. In addition it falls over as >>java 1.4 is set in the build.xml files and some of the source files >>contain java 1.5 key words. Also the 3rd party jars aren't found, they are >>under jars/lib but the build doesn't copy them to sys. Is there a how to >>guide somewhere on the web site that will take me through the build step >>by step... >> >>Thanks, >> >>Blaise. >>_______________________________________________ >>Cougaar-developers mailing list >>Cougaar-developers at cougaar.org >>http://cougaar.org/mailman/listinfo/cougaar-developers >> >> >> > > _______________________________________________ > Cougaar-developers mailing list > Cougaar-developers at cougaar.org > http://cougaar.org/mailman/listinfo/cougaar-developers > -------------- next part -------------- An HTML attachment was scrubbed... URL: http://cougaar.org/pipermail/cougaar-developers/attachments/20061204/279372b4/ant_workaround.html From blaise at idistro.com Thu Dec 7 03:33:57 2006 From: blaise at idistro.com (blaise@idistro.com) Date: Thu, 7 Dec 2006 00:33:57 -0800 (PST) Subject: Building Cougaar from source. In-Reply-To: <4574CC7E.50103@bbn.com> References: <841721380601122313n3d27013dt@mail.gmail.com> <200601161202.58889.twright@bbn.com> <200601171027.46606.twright@bbn.com> <58355.127.0.0.1.1165133499.squirrel@www.idistro.com> <45742A79.2070007@bbn.com> <4574CC7E.50103@bbn.com> Message-ID: <44584.127.0.0.1.1165480437.squirrel@www.idistro.com> That did the trick, the only additional thing that I needed to do was to export ANT_OPTS="-Xmx512m". Thanks, Blaise. > > As Aaron notes, the easiest option is to download a recent build and use > the top-level "build.xml" in the "cougaar-src.zip": > ant install > However, I just tried this and found several bugs. Attached below are > my notes and workarounds. > > The Perl script is fairly complex and difficult to use. I'd avoid it if > possible. > > Todd > > Aaron Helsinger wrote: >> The -r B12_1_5 arg is correct, but of course, it will only work if there >> actually is such a branch. The acme module does not have that branch. >> You can browse which tags are relevant when you use the web based CVS >> browser. >> >> These are standard CVS commands, and a web search should turn up some >> decent manuals. >> >> So the command that you gave checks ou the default branch of the acme >> module, HEAD. >> >> The build.xml files that come out of an individual project >> (/build.xml) are preset with module specific variables. >> >> Use the cougaar-src.zip zip file to get current build.xml files, >> including a parent level build.xml (to go in >> COUGAAR_INSTALL_PATH/build.xml) --- these files are in fact regenerated >> at every build with the current library dependencies, etc. Note however >> that this archive also includes all the source files, which you may not >> want. >> >> The (Perl) build script is in the build module: build/bin/build and uses >> the build/data/moduleTemplate.xml file to generate the per module >> build.xml, and productTemplate.xml to generate the parent level >> build.xml >> >> If you read the comments in the build.xml, they describe what they >> expect. >> In particular: >> The (correct) parent.xml will copy jars/lib into sys as necessary >> The build module installs its products in /clib so you wont get missing >> jars there. >> >> Basically, you should only need to: >> 1) Set JAVA_HOME and COUGAAR_INSTALL_PATH >> 2) checkout the modules under COUGAAR_INSTALL_PATH >> --- build is the main module for building other libraries, so you'll >> need that >> --- bootstrap, javaiopatch, core, util, and base get used by basically >> everything else, so you'll likely want those >> >> Any module that you dont want to build yourself, you can just get it >> from a recent build. >> Not all projects/modules on cougaar.org are built using this build >> process and conform to these conventions. The particular modules that >> these Ant build scripts know how to build are those that are configured >> in build/data/default.build. Note however that this data file is >> extensable, and you could add your own project there (as long as your >> directory structure conforms. >> >> I hope this helps, >> >> Aaron >> >> blaise at idistro.com wrote: >> >>>Hello, >>> >>>I've got a few questions about checking out and building cougaar >>> projects >>>from cvs. I've just checked out the source tree using the cvs commands >>> of >>>form: 'cvs -d :pserver:anonymous at cougaar.org:/cvsroot/acme checkout >>> acme' >>>for each project. Is this checking out the source from the current >>> active >>>dev branch, or should I be using the B12_1_5 branch if so how do I do >>> this >>>I tried the -r B12_1_5 tag but it didn't seem to work. >>> >>>Also can't get the source that I have to build, you'll have to excuse my >>>ignorance I'm used to just typing ant or mvn and having everything work >>>itself out from there. I had to take a top level build.xml file (that >>>lives under $COUGAAR_INSTALL_PATH) from one of the zipped distributions, >>>as I couldn't see how to get it out of cvs. I set the env variables >>>COUGAAR_INSTALL_PATH, and JAVA_HOME and typed 'ant'. The build couldn't >>>find classes in the tools.jar to link to. In addition it falls over as >>>java 1.4 is set in the build.xml files and some of the source files >>>contain java 1.5 key words. Also the 3rd party jars aren't found, they >>> are >>>under jars/lib but the build doesn't copy them to sys. Is there a how to >>>guide somewhere on the web site that will take me through the build step >>>by step... >>> >>>Thanks, >>> >>>Blaise. >>>_______________________________________________ >>>Cougaar-developers mailing list >>>Cougaar-developers at cougaar.org >>>http://cougaar.org/mailman/listinfo/cougaar-developers >>> >>> >>> >> >> _______________________________________________ >> Cougaar-developers mailing list >> Cougaar-developers at cougaar.org >> http://cougaar.org/mailman/listinfo/cougaar-developers >> > > From whzhang28 at 126.com Wed Dec 13 21:45:21 2006 From: whzhang28 at 126.com (=?gb2312?B?1cXOxLvb?=) Date: Thu, 14 Dec 2006 10:45:21 +0800 Subject: Ask for help of cougaar Message-ID: <4580BAB4.083FD4.15138> Dear friend, thanks for your cougaar platform. I am a Chinese student who is trying to research on Knowledge Based Multi-Agent System, and my experiment is based on cougaar. I am a beginner of cougaar and I need your help on programming under the cougar system. Now I have a question about how to pack a class-file into a .jar and it can also running regularly under the whole system. I tried to use the command ��jar cvfm..�� but that didn��t work. Please help me with your means of packing and I can't be thankful enough to you. I am looking forward to your reply. Thanks a lot. Yours, Sincerely Wendy -------------- next part -------------- An HTML attachment was scrubbed... URL: http://cougaar.org/pipermail/cougaar-developers/attachments/20061214/42cb0fe3/attachment.html From vengeance.storm at gmail.com Thu Dec 14 08:20:35 2006 From: vengeance.storm at gmail.com (Pan Xingzhi) Date: Thu, 14 Dec 2006 21:20:35 +0800 Subject: Ask for help of cougaar In-Reply-To: <-1040618602940713392@unknownmsgid> References: <-1040618602940713392@unknownmsgid> Message-ID: <841721380612140520m50dc7460sc013e18d53c097d8@mail.gmail.com> Okay I'll write in Chinese. After all that's my native language, too :) ��Cougaar��һЩ��Ը�� class�ļ��ô��cougaar��Ϥ��Java��Ϥ�� jar��ʹ�÷��£� �÷��jar {ctxu}[vfm0Mi] [jar-�ļ�] [manifest-�ļ�] [-C Ŀ¼] �ļ�� ... ѡ� -c ��µĴ浵 -t �г��浵��ݵ��б� -x չ��浵�е��ģ��еġ��ļ� -u ��Ѵ��ڵĴ浵 -v ��ϸ��׼�� -f ָ��浵�ļ�� -m ��Ա��ļ��ı��Ϣ -0 ֻ�洢��ʽ��δ��ZIPѹ��ʽ -M ��嵥��manifest��ļ� -i Ϊָ��jar�ļ��Ϣ -C �ı䵽ָ��Ŀ¼��Ұ��ļ�� һ��ļ��һ��Ŀ¼��ݹ鴦�� 嵥��manifest��ļ��ʹ浵�ļ��Ҫ��ָ��'m' �� 'f'��־ָ��ͬ˳�� ʾ��1��class�ļ��浵��һ��Ϊ 'classes.jar' �Ĵ浵�ļ��У� jar cvf classes.jar Foo.class Bar.class ʾ��2��һ��ڵ��嵥��manifest��ļ� 'mymanifest' �� foo/ Ŀ¼�µ�� ļ��浵��һ��Ϊ 'classes.jar' �Ĵ浵�ļ��У� jar cvfm classes.jar mymanifest -C foo/ . �绹��벻�ؿ�� 06-12-14��Ļ� д�� > > Dear friend, thanks for your cougaar platform. > > I am a Chinese student who is trying to research on Knowledge Based > Multi-Agent System, and my experiment is based on cougaar. I am a beginner > of cougaar and I need your help on programming under the cougar system. > > Now I have a question about how to pack a class-file into a .jar and it > can also running regularly under the whole system. I tried to use the > command 'jar cvfm..' but that didn't work. Please help me with your means of > packing and I can't be thankful enough to you. > > I am looking forward to your reply. Thanks a lot. > > Yours, > > Sincerely Wendy > > _______________________________________________ > Cougaar-developers mailing list > Cougaar-developers at cougaar.org > http://cougaar.org/mailman/listinfo/cougaar-developers > > > -------------- next part -------------- An HTML attachment was scrubbed... URL: http://cougaar.org/pipermail/cougaar-developers/attachments/20061214/dd228f2f/attachment.html From clholmes at vsticorp.com Tue Dec 19 14:34:19 2006 From: clholmes at vsticorp.com (Cathy L. Holmes) Date: Tue, 19 Dec 2006 14:34:19 -0500 Subject: Cougaar Evaluation Questions Message-ID: <2CBB676198347C4B89A33C4185129B1C540CB7@destroyer.VSTI.LOCAL> Hi, I am doing a trade study on several agent technologies, and would like to ask a few questions regarding Cougaar. Any assistance would be greatly appreciated! * Do you have any engineers that possess security clearances? * How often do you typically release new software? * What are your data throughput rates? * What kind of data capacity do you have? * Do you have any published benchmarks? * What is the largest system that is presently running Cougaar software? Thanks! Cathy Holmes Vision Systems and Technology -------------- next part -------------- An HTML attachment was scrubbed... URL: http://cougaar.org/pipermail/cougaar-developers/attachments/20061219/c5f7be70/attachment.html From ahelsing at bbn.com Tue Dec 19 14:57:17 2006 From: ahelsing at bbn.com (Aaron Helsinger) Date: Tue, 19 Dec 2006 14:57:17 -0500 Subject: Cougaar Evaluation Questions In-Reply-To: <2CBB676198347C4B89A33C4185129B1C540CB7@destroyer.VSTI.LOCAL> References: <2CBB676198347C4B89A33C4185129B1C540CB7@destroyer.VSTI.LOCAL> Message-ID: <4588441D.2060402@bbn.com> The cougaar-developers list that you have written to is a broad audience -- anyone doing Cougaar development and looking to trade tips and questions on developing Cougaar applications. Cougaar is not a single organization. There are many universities, companies, and private individuals that use the Cougaar architecture. Across all those groups, I know some engineers have clearances with their respective governments. There are many Cougaar projects, each of which can have its own release schedule. The 'core' Cougaar architecture is typically released at least once a year, with the next release expected in Spring 2007. For performance data and the like, I suggest looking at some of the published papers, listed here: http://cougaar.org/docman/?group_id=17 The actual data throughput rates / capacity depends highly on external things (content of the messages, the network, etc). Cougaar's messaging systems is highly flexible, allowing you to use many mechanisms for actual transport (Corba, RMI, etc..) and the throughput varies widely. I dont know what the largest currently operational Cougaar system is. Previous projects have had over 1000 large scale agents (the UltraLog program), and there are current projects of a smaller scale. But perhaps others can pipe in with their own current experience. I hope this helps you get started. Feel free to ask further questions, but Id ask that you join the mailing-list, to ensure that replies go to the whole community. Aaron Helsinger BBN Technologies Cathy L. Holmes wrote: > > Hi, > > > > I am doing a trade study on several agent technologies, and would like > to ask a few questions regarding Cougaar. Any assistance would be > greatly appreciated! > > > > * Do you have any engineers that possess security clearances? > * How often do you typically release new software? > * What are your data throughput rates? > * What kind of data capacity do you have? > * Do you have any published benchmarks? > * What is the largest system that is presently running Cougaar > software? > > > > Thanks! > > > > Cathy Holmes > > Vision Systems and Technology > > ------------------------------------------------------------------------ > > _______________________________________________ > Cougaar-developers mailing list > Cougaar-developers at cougaar.org > http://cougaar.org/mailman/listinfo/cougaar-developers > -------------- next part -------------- An HTML attachment was scrubbed... URL: http://cougaar.org/pipermail/cougaar-developers/attachments/20061219/b7a014be/attachment-0001.html From tcarrico at cougaarsoftware.com Thu Dec 21 09:58:20 2006 From: tcarrico at cougaarsoftware.com (Todd Carrico) Date: Thu, 21 Dec 2006 09:58:20 -0500 Subject: [Support-csc-info] Synchronization in Cougaar Message-ID: <02CF5C8267EAC44C9D9FDB1082335AEE5498F9@puma5.cougaarsoftware.com> There are several ways you can accomplish what you are looking to do, but probably the easiest way is to use the Attribute-Based Addressing (ABA) against a set of agents, managed through the community service. Regards, Todd ---------------------------------------------------------------------------- Todd M. Carrico, Ph.D. tcarrico at cougaarsoftware.com ---------------------------------------------------------------------------- -----Original Message----- From: support-csc-info-bounces at cougaar.org [mailto:support-csc-info-bounces at cougaar.org] On Behalf Of Zach.Lewkovicz at lip6.fr Sent: Thursday, December 21, 2006 6:02 AM To: support-csc-info at cougaar.org Subject: [Support-csc-info] Synchronization in Cougaar Bonjour, I am a PhD student and I intend to use cougaar for a multi-agent simulation. I would like to know if it is possible to use cougaar in a synchronized mode. If not, how can I use the message passing between agents in a synchronized way ? Thank you in advance, Lewkovicz Zach, Doctorant UPMC, LIP6 104 avenue du pr?sident Kennedy, 75016 Paris _______________________________________________ Support-csc-info mailing list Support-csc-info at cougaar.org http://cougaarforge.cougaar.org/mailman/listinfo/support-csc-info From Zach.Lewkovicz at lip6.fr Thu Dec 21 07:15:51 2006 From: Zach.Lewkovicz at lip6.fr (Zach.Lewkovicz@lip6.fr) Date: Thu, 21 Dec 2006 13:15:51 +0100 (CET) Subject: Synchronization in Cougaar Message-ID: <44252.132.227.203.140.1166703351.squirrel@mailia.lip6.fr> Bonjour, I am a PhD student and I intend to use cougaar for a multi-agent simulation. I would like to know if it is possible to use cougaar in a synchronized mode. If not, how can I use the message passing between agents in a synchronized way ? Thank you in advance, Lewkovicz Zach, Doctorant UPMC, LIP6 104 avenue du pr?sident Kennedy, 75016 Paris From twright at bbn.com Thu Dec 21 16:41:46 2006 From: twright at bbn.com (Todd Wright) Date: Thu, 21 Dec 2006 16:41:46 -0500 Subject: Synchronization in Cougaar In-Reply-To: <44252.132.227.203.140.1166703351.squirrel@mailia.lip6.fr> References: <44252.132.227.203.140.1166703351.squirrel@mailia.lip6.fr> Message-ID: <458AFF9A.3090305@bbn.com> Zach.Lewkovicz at lip6.fr wrote: > Bonjour, > > I am a PhD student and I intend to use cougaar for a multi-agent > simulation. I would like to know if it is possible to use cougaar in a > synchronized mode. If not, how can I use the message passing between > agents in a synchronized way ? Since you mentioned simulation, I'll assume you mean time synchronization, as opposed to coordination synchronization (e.g. transactions or group communications). I'll also assume you're running a single Cougaar node (JVM). This isn't required, but it greatly simplifies things. Cougaar includes support for Alarms, which plugins can use to schedule themselves to wake up at a future time. Alarms can specify either a "real" time, which matches "System.currentTimeMillis()", or a "demo" time, which is also called "simulation" time or "execution" time. By default, the demo time matches the real time: start at System.currentTimeMillis() rate is 1 second per second There's a "DemoControlService.setNodeTime(long time, double rate)" method to change the demo time and speed. For example, a plugin can add an alarm set to demo time of "12/31/2009". When that time arrives, or a plugin calls "setNodeTime" past 12/31/2009, the alarm will expire. The expire calls the plugin "execute()" method and tells the plugin to act. See the developers' guide for more information about how to use Alarm and the DemoControlService. If you need finer control, you can implement a custom, node-level service to support a timestamped event queue. As with alarms, your plugin could add Event objects to the queue, and the queue can sort the events and invoke callback methods to tell the plugins when an event is due. It'd be a very standard "global clock" simulator. Todd > > Thank you in advance, > > Lewkovicz Zach, Doctorant > UPMC, LIP6 > 104 avenue du pr?sident Kennedy, > 75016 Paris > > > _______________________________________________ > Cougaar-developers mailing list > Cougaar-developers at cougaar.org > http://cougaar.org/mailman/listinfo/cougaar-developers >