Menu
▾
▴
simspark-devel
|
From: Drew N. <dre...@ya...> - 2010-06-13 16:26:20
|
Hello all, I'm new to these lists, having only discovered the 3D Simulation League in April after visiting the Japan Open RoboCup event in Osaka. Since then I've spent countless hours learning what's required to make my own agent. Great fun. I found that there was some room to improve the public documentation of SimSpark and RoboCup 3D. I have made a bunch of edits to various wikis and would really appreciate if people more experienced that me would review them for accuracy. Firstly, the Wikipedia page RoboCup Simulation League exclusively covered the 2D sub-league. I moved that content to a new page and created another for the 3D sub-league. The previous page now links to these two new pages. I also fleshed out the SimSpark page. * http://en.wikipedia.org/wiki/RoboCup_Simulation_League * http://en.wikipedia.org/wiki/RoboCup_2D_Soccer_Simulation_League * http://en.wikipedia.org/wiki/RoboCup_3D_Soccer_Simulation_League * http://en.wikipedia.org/wiki/SimSpark On the SimSpark wiki I created a new page devoted to agent authoring. It contains a table of open source agents and base-code libraries. Please add any that are missing. * http://simspark.sourceforge.net/wiki/index.php/Agents In programming my own agent, I kept a list of where the SimSpark user manual was confusing, incomplete or possibly wrong. There's a new section beneath the User Manual download link on the wiki that lists these points: * http://simspark.sourceforge.net/wiki/index.php/Users_Manual Please take the time to review these pages for accuracy. Please make any changes directly, or discuss ideas for improvement on the relevant article's discussion page. For a full list of the changes I've made (there are other minor ones not listed above), see: * http://simspark.sourceforge.net/wiki/index.php/Special:Contributions/Drewnoakes * http://en.wikipedia.org/wiki/Special:Contributions/Drewnoakes It is my hope that these additions to Wikipedia and the SimSpark wiki will help extend the reach of these great projects as well as make it even easier for people to start programming their own agents. My sincere thanks to everyone who has contributed to SimSpark/rcssserver3d. Kind regards, Drew. |
|
From: Drew N. <dre...@ya...> - 2010-06-13 17:12:25
|
One question I've been pondering is whether a TeX-generated PDF is really the best medium for the bulk of the documentation when compared to a wiki. Here are the pros of each that I've come up with.
PDF
* Can be printed.
* Can be viewed offline.
* Fidelity of vector-based diagrams.
Wiki
* Editing is very easy, and only a click away when reading an article.
* Doesn't require post-edit compilation and release.
* Doesn't require commit access to the source code to make changes to the documentation.
* Everyone is always looking at the head version (I spent four weeks looking at an out-of-date PDF I found online). History is one click away and bad edits can easily be rolled back.
* Hyperlinking: within document / outside-in / inside-out.
* In situ discussion tabs for questions and ideas that sometimes result in quality improvements.
* More readily indexable by search engines, increasing project visibility.
* Wiki syntax is simpler than TeX.
* Can embed video from YouTube/vimeo/etc (I think the Wiki supports this).
* Support for translation into multiple languages (I think the Wiki supports this).
I am happy to spend a day carrying the content of the TeX files and images over to the Wiki if people agree this would be a good thing to do. As you say, documentation does tend to lag behind development, but if a larger audience of documenters are facilitated by a wiki, then the lag should be reduced and the quality and depth improved.
Drew.
________________________________
From: Peter Stone <ps...@cs...>
To: Drew Noakes <dr...@dr...>
Cc: sse...@li...; sim...@li...
Sent: Mon, 14 June, 2010 2:44:06
Subject: Re: [Sserver-three-d] Documentation and wikis
Drew,
Thank you very much for taking the time to document that.
Documentation always lags development, and having a newcomer document
difficulties at getting up to speed is always a valuble resource.
I hope the league can incorporate all of your suggestions quickly and
accurately.
Cheers,
Peter
>
> Hello all,
>
>
>
> I'm new to these lists, having only discovered the 3D Simulation League in April after visiting the Japan Open RoboCup
> event in Osaka. Since then I've spent countless hours learning what's required to make my own agent. Great fun.
>
>
>
> I found that there was some room to improve the public documentation of SimSpark and RoboCup 3D. I have made a bunch of
> edits to various wikis and would really appreciate if people more experienced that me would review them for accuracy.
>
>
>
> Firstly, the Wikipedia page RoboCup Simulation League exclusively covered the 2D sub-league. I moved that content to a new
> page and created another for the 3D sub-league. The previous page now links to these two new pages. I also fleshed out
> the SimSpark page.
>
>
>
> * [[http://en.wikipedia.org/wiki/RoboCup_Simulation_League]]
>
> * [[http://en.wikipedia.org/wiki/RoboCup_2D_Soccer_Simulation_League]]
>
> * [[http://en.wikipedia.org/wiki/RoboCup_3D_Soccer_Simulation_League]]
>
> * [[http://en.wikipedia.org/wiki/SimSpark]]
>
>
>
> On the SimSpark wiki I created a new page devoted to agent authoring. It contains a table of open source agents and
> base-code libraries. Please add any that are missing.
>
>
>
> * [[http://simspark.sourceforge.net/wiki/index.php/Agents]]
>
>
>
> In programming my own agent, I kept a list of where the SimSpark user manual was confusing, incomplete or possibly
> wrong. There's a new section beneath the User Manual download link on the wiki that lists these points:
>
>
>
> * [[http://simspark.sourceforge.net/wiki/index.php/Users_Manual]]
>
>
>
> Please take the time to review these pages for accuracy. Please make any changes directly, or discuss ideas for
> improvement on the relevant article's discussion page.
>
>
>
> For a full list of the changes I've made (there are other minor ones not listed above), see:
>
>
>
> * [[http://simspark.sourceforge.net/wiki/index.php/Special:Contributions/Drewnoakes]]
>
> * [[http://en.wikipedia.org/wiki/Special:Contributions/Drewnoakes]]
>
>
>
> It is my hope that these additions to Wikipedia and the SimSpark wiki will help extend the reach of these great projects as
> well as make it even easier for people to start programming their own agents. My sincere thanks to everyone who has
> contributed to SimSpark/rcssserver3d.
>
>
>
> Kind regards,
>
>
>
> Drew.
>
>
> ------------------------------------------------------------------------------
> ThinkGeek and WIRED's GeekDad team up for the Ultimate
> GeekDad Father's Day Giveaway. ONE MASSIVE PRIZE to the
> lucky parental unit. See the prize list and enter to win:
> http://p.sf.net/sfu/thinkgeek-promo_______________________________________________
> Sserver-three-d mailing list
> Sse...@li...
> https://lists.sourceforge.net/lists/listinfo/sserver-three-d
|
|
From: Simon R. <sra...@st...> - 2010-06-13 19:22:10
|
Sehr geehrter Drew Noakes, Am Sonntag 13 Juni 2010 19:12:18 schrieben Sie: > * Can be printed. > * Can be viewed offline. That's actually possible with a Wiki too, just look at how WikiBooks is doing it: http://en.wikibooks.org/w/index.php?title=Wikijunior:Big_Cats/Complete_Edition&action=edit This is a special page which includes all other pages as chapters into a single document when viewed, and can then be printed - also into a PDF file. The MediaWiki CSS style will automatically remove the Wiki decorations (menu, logo etc.) if the page is printed. It looks bad compared to a properly formated TeX document, and there is no Index, but it works. -- mit freundlichen Grüßen/regards/cordiali saluti Simon Raffeiner University of Applied Sciences Offenburg, Germany Department of Computer Science, RoboCup Team |
|
From: Drew N. <dre...@ya...> - 2010-06-14 05:43:59
|
Hi Simon, That looks like a very sensible way to deal with the printing/offline issue. In which case, I would revise the pros of using PDF documentation with TeX as: * Can (sort of) edit offline > It looks bad compared to a properly formated TeX document, and there is no Index, but it works. I think we might be able to create and index using a devoted page. And there's no way it'll look as good at a TeX document, but as you say the wiki uses different formatting for printable versions. Here's an example: http://simspark.sourceforge.net/wiki/index.php?title=Users_Manual&printable=yes I've had a few off-list emails in support of wiki based documentation and, as yet, nothing against the idea. I'm new to this group and not someone who should be deciding this kind of thing, so please if you do reply, do so to the group. Drew. ________________________________ From: Simon Raffeiner <sra...@st...> To: sim...@li...; Drew Noakes <dr...@dr...> Cc: Peter Stone <ps...@cs...>; sse...@li... Sent: Mon, 14 June, 2010 5:21:10 Subject: Re: [simspark-devel] [Sserver-three-d] Documentation and wikis Sehr geehrter Drew Noakes, Am Sonntag 13 Juni 2010 19:12:18 schrieben Sie: > * Can be printed. > * Can be viewed offline. That's actually possible with a Wiki too, just look at how WikiBooks is doing it: http://en.wikibooks.org/w/index.php?title=Wikijunior:Big_Cats/Complete_Edition&action=edit This is a special page which includes all other pages as chapters into a single document when viewed, and can then be printed - also into a PDF file. The MediaWiki CSS style will automatically remove the Wiki decorations (menu, logo etc.) if the page is printed. It looks bad compared to a properly formated TeX document, and there is no Index, but it works. -- mit freundlichen Grüßen/regards/cordiali saluti Simon Raffeiner University of Applied Sciences Offenburg, Germany Department of Computer Science, RoboCup Team |
|
From: Joschka B. <jos...@am...> - 2010-06-14 10:27:31
|
Hi Drew, thanks a lot for your contributions, and for taking the initiative on this issue. On Jun 14, 2010, at 2:43 PM, Drew Noakes wrote: > > I've had a few off-list emails in support of wiki based documentation and, as yet, nothing against the idea. I'm new to this group and not someone who should be deciding this kind of thing, so please if you do reply, do so to the group. I think having the manual in the Wiki would be great! We could still have a nice PDF version every once in a while, but focus on the Wiki which should be easier to keep up to date. Would you be willing to go ahead and start this? I'm sure people will help once the first pages are there, but it's always good if someone takes the lead. Cheers, Joschka |
|
From: Drew N. <dre...@ya...> - 2010-06-14 14:47:18
|
Hi Joschka,
I'll get started in the next day or so. No doubt I'll have many questions, so I'll add them to the wiki itself and ask people more knowledgeable than me to fill in the blanks.
I saw somewhere a task along the lines of "update TeX files with TEXT_INSTEAD_OF_A_MANUAL". Does this text file represent the most up-to-date information? I will be sure to draw from all sources I can find, but if there are conflicts I'd like to know which source is more authoritative.
Also, does anyone have any documentation about the monitor protocol? If not then I will reverse it from TrainerCommandParser. I was going to ask the list whether it would be possible to add the ability to position the ball exactly for machine learning purposes, only to find mention of this interface in a changelog somewhere. It'd be great to have it detailed on the wiki.
Drew.
________________________________
From: Joschka Boedecker <jos...@am...>
To: Drew Noakes <dr...@dr...>
Cc: Simspark Devel ML <sim...@li...>; sse...@li...
Sent: Mon, 14 June, 2010 20:27:19
Subject: Re: [simspark-devel] [Sserver-three-d] Documentation and wikis
Hi Drew,
thanks a lot for your contributions, and for taking the initiative on this issue.
On Jun 14, 2010, at 2:43 PM, Drew Noakes wrote:
>
>I've had a few off-list emails in support of wiki based documentation and, as yet, nothing against the idea. I'm new to this group and not someone who should be deciding this kind of thing, so please if you do reply, do so to the group.
I think having the manual in the Wiki would be great! We could still have a nice PDF version every once in a while, but focus on the Wiki which should be easier to keep up to date.
Would you be willing to go ahead and start this? I'm sure people will help once the first pages are there, but it's always good if someone takes the lead.
Cheers,
Joschka
|
|
From: Joschka B. <jos...@am...> - 2010-06-15 01:04:17
|
Hi Drew and all, On Jun 14, 2010, at 11:47 PM, Drew Noakes wrote: > > I'll get started in the next day or so. Excellent! > No doubt I'll have many questions, so I'll add them to the wiki itself and ask people more knowledgeable than me to fill in the blanks. > OK, sounds good. > I saw somewhere a task along the lines of "update TeX files with TEXT_INSTEAD_OF_A_MANUAL". Does this text file represent the most up-to-date information? I will be sure to draw from all sources I can find, but if there are conflicts I'd like to know which source is more authoritative. > The TEXT_INSTEAD_OF_A_MANUAL file was used as the basis for the user manual. However, not all of the information made it into the tex files (we planned a server developer's manual that was supposed to contain some of that information, see also below). So I guess in places where there is overlap, the manual should be more recent. > Also, does anyone have any documentation about the monitor protocol? Part of it is documented in the TEXT_INSTEAD_OF_A_MANUAL. In addition, about two years ago Carlos Bustamante was kind enough to document the monitor protocol further. Unfortunately, the information never made it into the manual (it was supposed to go into the developer's manual, but so far, we haven't gotten started on that one yet :-( ). You can find his draft at [1]. It might be incomplete, and possibly slightly out of date, but it's a good start. > If not then I will reverse it from TrainerCommandParser. I was going to ask the list whether it would be possible to add the ability to position the ball exactly for machine learning purposes, only to find mention of this interface in a changelog somewhere. It'd be great to have it detailed on the wiki. > If I'm not mistaken, it is also described in the TEXT_INSTEAD_OF_A_MANUAL file. We should also document that it is possible to run agents as plugins directly in the simulator process, with no network communication required (example is given in the soccerbotbehavior in rcssserver3d/plugin/soccer/agentintegration). This should also be interesting for machine learning and debugging purposes, and it might be another one of those useful but not very well known features of the simulator. I mention it in the overview paper I wrote for the SIMPAR 2008 workshop [2], but that might be its only mention I'm afraid. Just as a general note, not directly concerning the documentation, I wanted to let people know that we have started development on the integration of the Bullet physics engine into the simulator as an alternative to ODE. My colleague Richard Keely has kindly taken on that task, and I'll try to assist. Best regards, Joschka [1] http://jeap-res.ams.eng.osaka-u.ac.jp/~joschka/simspark/monitorprotocol.pdf [2] http://monicareggiani.net/simpar2008/RoboCupSimulators/SIMPAR_simspark.pdf |
|
From: Drew N. <dre...@ya...> - 2010-06-17 08:32:14
|
The bulk of the work has been done in porting the documentation across to the Wiki. I have broken it up into what felt like sensible topics to me, and I'm open to alternative ideas. I've spent a while going through trying to cross-reference articles to increase visibility of the new content for visitors. There is some information on this page that shows what new pages were created, and what sections of the PDF I didn't port over because they seemed out of date or particular to a paper document. http://simspark.sourceforge.net/wiki/index.php/Users_Manual#Wiki_Version I have also left several TODO markers accompanied by short questions on a few pages. Much of the documentation was out of date and it would be great to have more experienced people read it through. I still have to reconcile my errata. I'll do that soon. Also Joschka, I took a screenshot of a diagram that was included in your SIMPAR paper and included it on the wiki. I can remove it if it doesn't have the appropriate license for use on the wiki. Apologies, but that only crossed my mind after I'd joyfully copied your work! I've made a quick job of putting more content on the main page under slightly different groupings. Any feedback, good or bad, is appreciated. http://simspark.sourceforge.net/wiki/index.php/Main_Page > We should also document that it is possible to run agents as plugins directly in the simulator process... This has been done. > ...about two years ago Carlos Bustamante was kind enough to document the monitor protocol further... That PDF is a great start, but it only covers messages from the server to the monitor. I am particularly interested in those messages that I can send to the server on port 3200 in order to perform machine learning. Any pointers to information on that would be great. All the best, Drew. ________________________________ From: Joschka Boedecker <jos...@am...> To: Drew Noakes <dr...@dr...> Cc: 3D Server ML <sse...@li...>; Simspark Devel ML <sim...@li...>; Richard Keely <rc...@gm...> Sent: Tue, 15 June, 2010 11:04:08 Subject: Re: [simspark-devel] [Sserver-three-d] Documentation and wikis Hi Drew and all, On Jun 14, 2010, at 11:47 PM, Drew Noakes wrote: > > I'll get started in the next day or so. Excellent! > No doubt I'll have many questions, so I'll add them to the wiki itself and ask people more knowledgeable than me to fill in the blanks. > OK, sounds good. > I saw somewhere a task along the lines of "update TeX files with TEXT_INSTEAD_OF_A_MANUAL". Does this text file represent the most up-to-date information? I will be sure to draw from all sources I can find, but if there are conflicts I'd like to know which source is more authoritative. > The TEXT_INSTEAD_OF_A_MANUAL file was used as the basis for the user manual. However, not all of the information made it into the tex files (we planned a server developer's manual that was supposed to contain some of that information, see also below). So I guess in places where there is overlap, the manual should be more recent. > Also, does anyone have any documentation about the monitor protocol? Part of it is documented in the TEXT_INSTEAD_OF_A_MANUAL. In addition, about two years ago Carlos Bustamante was kind enough to document the monitor protocol further. Unfortunately, the information never made it into the manual (it was supposed to go into the developer's manual, but so far, we haven't gotten started on that one yet :-( ). You can find his draft at [1]. It might be incomplete, and possibly slightly out of date, but it's a good start. > If not then I will reverse it from TrainerCommandParser. I was going to ask the list whether it would be possible to add the ability to position the ball exactly for machine learning purposes, only to find mention of this interface in a changelog somewhere. It'd be great to have it detailed on the wiki. > If I'm not mistaken, it is also described in the TEXT_INSTEAD_OF_A_MANUAL file. We should also document that it is possible to run agents as plugins directly in the simulator process, with no network communication required (example is given in the soccerbotbehavior in rcssserver3d/plugin/soccer/agentintegration). This should also be interesting for machine learning and debugging purposes, and it might be another one of those useful but not very well known features of the simulator. I mention it in the overview paper I wrote for the SIMPAR 2008 workshop [2], but that might be its only mention I'm afraid. Just as a general note, not directly concerning the documentation, I wanted to let people know that we have started development on the integration of the Bullet physics engine into the simulator as an alternative to ODE. My colleague Richard Keely has kindly taken on that task, and I'll try to assist. Best regards, Joschka [1] http://jeap-res.ams.eng.osaka-u.ac.jp/~joschka/simspark/monitorprotocol.pdf [2] http://monicareggiani.net/simpar2008/RoboCupSimulators/SIMPAR_simspark.pdf |
|
From: Peter S. <ps...@cs...> - 2010-06-13 16:44:18
|
Drew, Thank you very much for taking the time to document that. Documentation always lags development, and having a newcomer document difficulties at getting up to speed is always a valuble resource. I hope the league can incorporate all of your suggestions quickly and accurately. Cheers, Peter > > Hello all, > > > > I'm new to these lists, having only discovered the 3D Simulation League in April after visiting the Japan Open RoboCup > event in Osaka. Since then I've spent countless hours learning what's required to make my own agent. Great fun. > > > > I found that there was some room to improve the public documentation of SimSpark and RoboCup 3D. I have made a bunch of > edits to various wikis and would really appreciate if people more experienced that me would review them for accuracy. > > > > Firstly, the Wikipedia page RoboCup Simulation League exclusively covered the 2D sub-league. I moved that content to a new > page and created another for the 3D sub-league. The previous page now links to these two new pages. I also fleshed out > the SimSpark page. > > > > * [[http://en.wikipedia.org/wiki/RoboCup_Simulation_League]] > > * [[http://en.wikipedia.org/wiki/RoboCup_2D_Soccer_Simulation_League]] > > * [[http://en.wikipedia.org/wiki/RoboCup_3D_Soccer_Simulation_League]] > > * [[http://en.wikipedia.org/wiki/SimSpark]] > > > > On the SimSpark wiki I created a new page devoted to agent authoring. It contains a table of open source agents and > base-code libraries. Please add any that are missing. > > > > * [[http://simspark.sourceforge.net/wiki/index.php/Agents]] > > > > In programming my own agent, I kept a list of where the SimSpark user manual was confusing, incomplete or possibly > wrong. There's a new section beneath the User Manual download link on the wiki that lists these points: > > > > * [[http://simspark.sourceforge.net/wiki/index.php/Users_Manual]] > > > > Please take the time to review these pages for accuracy. Please make any changes directly, or discuss ideas for > improvement on the relevant article's discussion page. > > > > For a full list of the changes I've made (there are other minor ones not listed above), see: > > > > * [[http://simspark.sourceforge.net/wiki/index.php/Special:Contributions/Drewnoakes]] > > * [[http://en.wikipedia.org/wiki/Special:Contributions/Drewnoakes]] > > > > It is my hope that these additions to Wikipedia and the SimSpark wiki will help extend the reach of these great projects as > well as make it even easier for people to start programming their own agents. My sincere thanks to everyone who has > contributed to SimSpark/rcssserver3d. > > > > Kind regards, > > > > Drew. > > > ------------------------------------------------------------------------------ > ThinkGeek and WIRED's GeekDad team up for the Ultimate > GeekDad Father's Day Giveaway. ONE MASSIVE PRIZE to the > lucky parental unit. See the prize list and enter to win: > http://p.sf.net/sfu/thinkgeek-promo_______________________________________________ > Sserver-three-d mailing list > Sse...@li... > https://lists.sourceforge.net/lists/listinfo/sserver-three-d |
|
From: Peter S. <ps...@cs...> - 2010-06-13 17:46:29
|
Drew,
I agree that a wiki would be useful for this, but I'll let the rest of
the community chime in.
Will you be at the competition in Singapore next week? If so, that
would be a great time to have this conversation in real time and with
all the relevant people involved...
Peter
>
>
> One question I've been pondering is whether a TeX-generated PDF is really the best medium for the bulk of the documentation
> when compared to a wiki. Here are the pros of each that I've come up with.
>
>
>
> PDF
>
>
>
> * Can be printed.
>
> * Can be viewed offline.
>
> * Fidelity of vector-based diagrams.
>
>
>
> Wiki
>
>
>
> * Editing is very easy, and only a click away when reading an article.
>
> * Doesn't require post-edit compilation and release.
>
> * Doesn't require commit access to the source code to make changes to the documentation.
>
> * Everyone is always looking at the head version (I spent four weeks looking at an out-of-date PDF I found
> online). History is one click away and bad edits can easily be rolled back.
>
> * Hyperlinking: within document / outside-in / inside-out.
>
> * In situ discussion tabs for questions and ideas that sometimes result in quality improvements.
>
> * More readily indexable by search engines, increasing project visibility.
>
> * Wiki syntax is simpler than TeX.
>
> * Can embed video from YouTube/vimeo/etc (I think the Wiki supports this).
>
> * Support for translation into multiple languages (I think the Wiki supports this).
>
>
>
> I am happy to spend a day carrying the content of the TeX files and images over to the Wiki if people agree this would be a
> good thing to do. As you say, documentation does tend to lag behind development, but if a larger audience of documenters
> are facilitated by a wiki, then the lag should be reduced and the quality and depth improved.
>
>
>
> Drew.
>
>
>
> ---------------------------------------------------------------------------------------------------------------------------
>
> From: Peter Stone <ps...@cs...>
> To: Drew Noakes <dr...@dr...>
> Cc: sse...@li...; sim...@li...
> Sent: Mon, 14 June, 2010 2:44:06
> Subject: Re: [Sserver-three-d] Documentation and wikis
> Drew,
> Thank you very much for taking the time to document that.
> Documentation always lags development, and having a newcomer document
> difficulties at getting up to speed is always a valuble resource.
> I hope the league can incorporate all of your suggestions quickly and
> accurately.
> Cheers,
> Peter
> >
> > Hello all,
> >
> >
> >
> > I'm new to these lists, having only discovered the 3D Simulation League in April after visiting the Japan Open RoboCup
> > event in Osaka. Since then I've spent countless hours learning what's required to make my own agent. Great fun.
> >
> >
> >
> > I found that there was some room to improve the public documentation of SimSpark and RoboCup 3D. I have made a bunch of
> > edits to various wikis and would really appreciate if people more experienced that me would review them for accuracy.
> >
> >
> >
> > Firstly, the Wikipedia page RoboCup Simulation League exclusively covered the 2D sub-league. I moved that content to a
> new
> > page and created another for the 3D sub-league. The previous page now links to these two new pages. I also fleshed out
> > the SimSpark page.
> >
> >
> >
> > * [[[[http://en.wikipedia.org/wiki/RoboCup_Simulation_League]]]]
> >
> > * [[[[http://en.wikipedia.org/wiki/RoboCup_2D_Soccer_Simulation_League]]]]
> >
> > * [[[[http://en.wikipedia.org/wiki/RoboCup_3D_Soccer_Simulation_League]]]]
> >
> > * [[[[http://en.wikipedia.org/wiki/SimSpark]]]]
> >
> >
> >
> > On the SimSpark wiki I created a new page devoted to agent authoring. It contains a table of open source agents and
> > base-code libraries. Please add any that are missing.
> >
> >
> >
> > * [[[[http://simspark.sourceforge.net/wiki/index.php/Agents]]]]
> >
> >
> >
> > In programming my own agent, I kept a list of where the SimSpark user manual was confusing, incomplete or possibly
> > wrong. There's a new section beneath the User Manual download link on the wiki that lists these points:
> >
> >
> >
> > * [[[[http://simspark.sourceforge.net/wiki/index.php/Users_Manual]]]]
> >
> >
> >
> > Please take the time to review these pages for accuracy. Please make any changes directly, or discuss ideas for
> > improvement on the relevant article's discussion page.
> >
> >
> >
> > For a full list of the changes I've made (there are other minor ones not listed above), see:
> >
> >
> >
> > * [[[[http://simspark.sourceforge.net/wiki/index.php/Special:Contributions/Drewnoakes]]]]
> >
> > * [[[[http://en.wikipedia.org/wiki/Special:Contributions/Drewnoakes]]]]
> >
> >
> >
> > It is my hope that these additions to Wikipedia and the SimSpark wiki will help extend the reach of these great projects
> as
> > well as make it even easier for people to start programming their own agents. My sincere thanks to everyone who has
> > contributed to SimSpark/rcssserver3d.
> >
> >
> >
> > Kind regards,
> >
> >
> >
> > Drew.
> >
> >
> > ------------------------------------------------------------------------------
> > ThinkGeek and WIRED's GeekDad team up for the Ultimate
> > GeekDad Father's Day Giveaway. ONE MASSIVE PRIZE to the
> > lucky parental unit. See the prize list and enter to win:
> > [[http://p.sf.net/sfu/thinkgeek-promo_______________________________________________]]
> > Sserver-three-d mailing list
> > [[Sse...@li...]]
> > [[https://lists.sourceforge.net/lists/listinfo/sserver-three-d]]
>
>
>
|
|
From: Drew N. <dre...@ya...> - 2010-06-14 03:44:07
|
> I agree that a wiki would be useful for this, but I'll let the rest of the community chime in. I look forward to hearing people's ideas. > Will you be at the competition in Singapore next week? Sadly not. I have the time, but my passport is locked away in a consulate along with a visa application. The Japan Open matches were streamed live via www.ustream.tv. Will that be the case from Singapore? ________________________________ From: Peter Stone <ps...@cs...> To: Drew Noakes <dr...@dr...> Cc: sse...@li...; sim...@li... Sent: Mon, 14 June, 2010 3:46:15 Subject: Re: [Sserver-three-d] Documentation and wikis Drew, I agree that a wiki would be useful for this, but I'll let the rest of the community chime in. Will you be at the competition in Singapore next week? If so, that would be a great time to have this conversation in real time and with all the relevant people involved... Peter |
×
Want the latest updates on software, tech news, and AI?
Get latest updates about software, tech news, and AI from SourceForge directly in your inbox once a month.
Thanks for helping keep SourceForge clean.
X