[X3D-Public] The Network Sensor is not enough
Christoph Valentin
christoph.valentin at gmx.at
Sat Feb 12 10:19:31 PST 2011
Hi Sven-Erik
Unfortunately, I don't have a copy of the IEEE DIS standard. Hence the
following statements will not be based on facts but just on assumptions and
impressions - and on the X3D DIS API (aka X3D DIS Component), which is
publicly available.
I think, a car driver simulator is one thing, but a railway simulation is
another thing.
In railway simulations, we have a 1-dimensional kinematics "along the
track", we have bogies, we have jointed vehicles, vehicles can be combined
to trains, trains can be splitted, and so on.
I'm not 100% sure, but from what I think to know about DIS, DIS will not be
flexible/extensible enough to model such things.
>From my point of view, the whole "SrrTrains" project is mainly a thought
experiment, but I have started to notice a little bit interest,.........
Much fun with your car simulator, of course :-)
Christoph
>
> -------- Original-Nachricht --------
> Datum: Thu, 10 Feb 2011 09:09:42 +0100
> Von: Sven-Erik Tiberg <Sven-Erik.Tiberg at ltu.se>
> An: "'Christoph Valentin'" <christoph.valentin at gmx.at>
> CC: "x3d-public at web3d.org" <x3d-public at web3d.org>
> Betreff: RE: [X3D-Public] The Network Sensor is not enough
>
> Hi Christoph FYI: got a student working with
> his thesis about driversimulator and a former student that has a lot of
> interest in development for our driversimulators and recently took a
> position to develope flight-controllers and simulators as senior
> developer. The mission are to get a running driving
> simulator för traing of driving on snow and ice roads and to evaluate
> drivers capability to handle traficsituation after having f.ex. a stroke
> or any medical disfunction or high age. http://wbsp.arb.ltu.se/Motionbase
> We will initially use www.CarSim.com with custom
> made simulink modules for UDP-stream of comma separated floating point
> states to control a motionsimulator. The UDP cs-state stream
> will be changed to XMPP and disXML defined states. This task
> are on my desk and I'm starting with setting up the XMPP client and
> server enviroment using strophejs (
> http://code.stanziq.com/strophe/ ) and ejabberd (
> http://www.ejabberd.im/ ). StropeJS
> with XMPP/disXML can be implemented in most X3DBrowsers. Porting
> to PyXMPP opens up for more clients. The "challange" are to find
> a fast XML resolver to code / decode states from the OpenDIS XML scema.
> After getting an understanding of strophejs-disXML we
> will move on to libstrophe and compile it into matlab mex file to be
> used in simulink and to extend our custom made controlsystem for the
> motionbase 6 dof system. Getting there we have disXML/XMPP
> running i our driversimulator and can extend it with X3Dbrowsers and
> PDA's and ... PS. it's a great source of information at NPS that
> supports this development.
> Keep you posted on this. MVG Sven-Erik Tiberg
> From: x3d-public-bounces at web3d.org
> [mailto:x3d-public-bounces at web3d.org] On Behalf Of Christoph Valentin
> Sent: den 2 februari 2011 08:07
> Cc: x3d-public at web3d.org
> Subject: Re: [X3D-Public] The Network Sensor is not enough
>
> Thank you for the voluntary joining up.
>
> So, the show will go on.
>
> >
> > -------- Original-Nachricht --------
> > Datum: Sat, 08 Jan 2011 04:00:22 +0100
> > Von: "Christoph Valentin" <christoph.valentin at gmx.at>
> > An: x3d-public at web3d.org
> > Betreff: [X3D-Public] The Network Sensor is not enough
> >
> > Dear members of the X3D-public
> >
> > When comparing Network sensor and DIS, you will find, that DIS is
> > quite specialized, but it's easy for the developer of the scene to
> > use DIS, where the Network Sensor is very general, but the scene
> > author has to define and implement a lot of specifics, before he can
> > use the Network Sensor.
> >
> > This was my impression at least.
> >
> > Such topics like
> > - reusability of models and modules (given a module is a part of
> > the landscape)
> > in different scenes from different authors
> > - implementing central services, that are (currently) not
> > available on the collaboration server
> > - interactivity and animation
> >
> > are not very well defined, so each company, each framework, each
> > author uses very different approaches.
> >
> > It's my impression, at least.
> >
> > If you agree to this, the following text might be interesting for
> > you, otherwise you can stop reading here.
> >
> > Since IMHO the Network Sensor has a lot of advantages, too, I think
> > it would be worth to play around with the possibilities (goal is an
> > evolution of the standard) and started an open source project, which is
> > mainly a playground.
> >
> > A short introduction at:
> > http://smuos.wordpress.com/2011/01/06/smuos-and-the-srr-framework/
> > The project at: http://sourceforge.net/projects/simulrr
> >
> > This playground could be used by others interested, too.
> >
> > I know the sourceforge project has still a lot of weaknesses (poor
> > chat, poor GUI, written entirely in ECMAScript, uses currently only
> > one multiuser server......), but I decided to post NOW at
> > X3D-Public, because NOW we have a lot of discussions regarding
> > "doing things within the scene" or "doing things outside the scene"
> > (because of the declarative 3D discussion) and it fits here.
> >
> > It's a private hobby project and I am not backed by a company, but
> > it *could* become a topic for my employer.
> >
> > Have fun
> > Christoph
> >
> >
> > --
> > Neu: GMX De-Mail - Einfach wie E-Mail, sicher wie ein Brief!
> > Jetzt De-Mail-Adresse reservieren: http://portal.gmx.net/de/go/demail
> >
>
>
>
> --
> NEU: FreePhone - kostenlos mobil telefonieren und surfen!
> Jetzt informieren: http://www.gmx.net/de/go/freephone
--
Schon gehört? GMX hat einen genialen Phishing-Filter in die
Toolbar eingebaut! http://www.gmx.net/de/go/toolbar
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://web3d.org/pipermail/x3d-public_web3d.org/attachments/20110212/9e90305d/attachment.html>
More information about the X3D-Public
mailing list