You received this message because you are subscribed to the Google
Groups "org-concord-sensor" group.
To post to this group, send email to org-conco...@googlegroups.com
To unsubscribe from this group, send email to
For more options, visit this group at
Google Code project for org-concord-sensor: http://code.google.com/p/org-concord-sensor/
The use case is basically the ability inserting netlogo sensor
components in a netlogo project.
As its only parameter the sensor components receives the port # to
identify which sensor should represent this netlogo component.
The netlogo component would then continuously display the sensor value
returned by the sensor identified by port #.
Now the goal is to allow user to identify whichever sensor he/she
wants. I thought port # is the way to go, but if as you say there are
some sensors that use different values for external and internal ports
that could be problematic. Also we need a way to identify sensors that
are attached to different USB inputs of a same computer.
That said, for now I can find a way around this by just hard coding it
for the specific need of augmented reality project which uses a single
type of sensor.
But we may want to come up with a better more generic
way of doing this for future projects.
A note I posted to the visual-leaders email list:
A note: while this works when running NetLogo as an application NetLogo extensions (with native libraries) do NOT work withNetLogo applets.
At 10:39 AM -0500 2/23/12, Robert Tinker wrote:
>Is the implication that this would not work in WISE4 because it
The NetLogo 5.0 manual page on applets states:
Many extensions can be used in applets. Simply place the folder containing
the extension jar in the same folder as the model.
Extensions that require native libraries don't work from applets. This includes
the QTJ and GoGo extensions.
It is possible this could be fixed but my experience in getting the sensor applet working an all browsers with native librariesis that this can be quite tricky.
>What are other implications?
Also in the short-medium term converting selected NetLogo models to html5 and using these directly with the sensor applet wouldwork.
However until the google grant gets sensors working in browsers on iOS and Android systems we won't be able to disseminate evenHTML5 models using sensors on tablet and smartphone browsers.