Re: [simspark-devel] New User Manual and Wiki

[Stefan G. <gla...@gm...>]

Hi Hedayat,

thanks a lot for your quick and clear answer!
I expected to old value already to represent the value you described now ;)
So overall the accelerometer description in the manual and wiki fits in 
its current state already the new value.

Thanks,
Stefan


Am 13.05.2011 16:07, schrieb Hedayat Vatankhah:
> Hi Stefan,
>
> /*Stefan Glaser <gla...@gm...>*/ wrote on 05/12/2011 6:15:33 
> PM +0450:
>> Hallo all,
>>
>> I'm currently updating the descriptions in the wiki according to the new
>> release. I was able to look up / get most of the information I was
>> looking for, but two questions are still not clear to me, which I now
>> want to ask you in this mail.
> Thanks a lot for your efforts :)
>
>> First of all, I wanted to ask for the unit transmitted by the
>> accelerometer. I wanted to document that it now provides RAW-data, but
>> it's unclear to me, what's the real meaning of that. Can someone give me
>> a pointer on that?
> It is the difference of velocity for the body part reported by ODE 
> divided by the spent time. AFAIK, ODE uses SI units, so the reported 
> acceleration should be in m/s^2.
>
> About lines, probably Yuan can provide some help. :P
>
> Good luck!
> Hedayat
>
>> The socond problem I'm unclear about is the description of the field
>> lines. I visualized the field lines to get some idea, where they are
>> located and why the agent sees so much of them. Then I realized that the
>> middle circle is modelled with 10 small field lines. If the complete
>> circle is seen (what is often the case for most of the robots during a
>> game), this results in 20 coordinates located around a relatively small
>> spot in a very simple arrangment, also supported by the middle line. I
>> wonder about the purpose of putting in this kind of modelling of the
>> middle circle. 20 coordinates is a lot of traffic - in fact close to 50%
>> of the currently visible field lines are needed to model the middle
>> circle. I'm also not sure how realistic this is compared to a real
>> scenario... but I have no experience with that. But since I expect the
>> vision-errors to be applied separately on each coordinate, it should be
>> absolutely no problem to do e.g. a camera calibration within a few cycles.
>> Overall I struggle a bit with giving a clear decription to the field
>> lines. The normal lines don't need a special description, but if the
>> middle circle stays this way, I have to add some special description to
>> the arrangement of these lines.
>>
>> Best regards,
>> Stefan
>>
>> ------------------------------------------------------------------------------
>> Achieve unprecedented app performance and reliability
>> What every C/C++ and Fortran developer should know.
>> Learn how Intel has extended the reach of its next-generation tools
>> to help boost performance applications - inlcuding clusters.
>> http://p.sf.net/sfu/intel-dev2devmay
>> _______________________________________________
>> Simspark Generic Physical MAS Simulator
>> simspark-devel mailing list
>> sim...@li...
>> https://lists.sourceforge.net/lists/listinfo/simspark-devel