TWiki home VRJ Wiki > Juggler > PositionalInputUnitsAndScaling (r1.1 vs. r1.3) VRJ Wiki webs:
Juggler | VRJPlanning | Main | TWiki | Test
Juggler . { Home | Changes | Index | Search | Go }
 <<O>>  Difference Topic PositionalInputUnitsAndScaling (r1.3 - 16 Sep 2002 - AllenBierbaum)

META TOPICPARENT WebHome

Background

Line: 24 to 24

- All devices must be configured to return positional input in the same units and coordinate frame. (this isn't much of a restriction since this was already required anyway)

Added:
>
>		 Data flow:

The data would flow something like this...

Pos data => xform(device xform) => scale(gadget scalar * app scalar) => final pos
(flock bird)


Notes

- Helpers would be provided in the configuration chunks and in the application callback for setting and returning unit conversion factors. For example in a configuration chunk, a user would be able to select from a pull-down list of available options like: meters, centi-meters, inches, feet. In an application, the user could return something like: "return gadget::Unit::feet" This would be an alias for the actual conversion factor.

Changed:
<
<		 [Could you provide some example code, C++ or otherwise, that demonstrates what you mean? I don't quite understand what the user is returning and to whom it is being returned. --ph]
>
>		 The base class would have: 
float vrj::App::getAppUnitScalar()
{ return gadget::Units::Feet; }

Then user applications could override this with any unit they like: 

float UserApp::getAppUnitScalar()
{ return gadget::Units::Meter; }

I am not sure on the method name yet (any suggestions??), but this would be the basic idea.


Comments


 <<O>>  Difference Topic PositionalInputUnitsAndScaling (r1.2 - 16 Sep 2002 - PatrickHartling)

META TOPICPARENT WebHome

Background

Line: 29 to 29

- Helpers would be provided in the configuration chunks and in the application callback for setting and returning unit conversion factors. For example in a configuration chunk, a user would be able to select from a pull-down list of available options like: meters, centi-meters, inches, feet. In an application, the user could return something like: "return gadget::Unit::feet" This would be an alias for the actual conversion factor.

Added:
>
>		 [Could you provide some example code, C++ or otherwise, that demonstrates what you mean? I don't quite understand what the user is returning and to whom it is being returned. --ph]

Comments

  • Why use meters as the base (internal) VR Juggler units? (why not feet, inches, centimeters, etc)
Changed:
<
<		 I chose meters because it is the international standard unit of measurement. It is easy for most people to use and seemed liked a better choice then the other units.
>
>		 I chose meters because it is the international standard unit of measurement. It is easy for most people to use and seemed liked a better choice than the other units.


 <<O>>  Difference Topic PositionalInputUnitsAndScaling (r1.1 - 16 Sep 2002 - AllenBierbaum)
Line: 1 to 1
Added:
>
>
META TOPICPARENT WebHome

Background

There is currently an issue with gadgeteer and VR Juggler where applications can not easily move between systems that are using different units for their base configuration units (meters vs. feet).

We need a way to allow applications to move transparently between systems without regards to what units that system has been configured with.

Proposed solution

Configuration

Positional devices Translation, rotation, and scale to get to common units for the given VR system
Gadgeteer Scale value to convert for local system base units to common Juggler base units (meters)
VRJ Apps Member function returns a scale value to convert from VRJ base units (meters) to whatever units application may be in

This configuration method allows for:

- Local systems to be configured using whatever base measurement units they like. People can configure their systems with feet, meters, or even some imaginary base unit that only exists in their system.

- Applications can use any measurement units that they like.

Restrictions:

- All devices must be configured to return positional input in the same units and coordinate frame. (this isn't much of a restriction since this was already required anyway)

Notes

- Helpers would be provided in the configuration chunks and in the application callback for setting and returning unit conversion factors. For example in a configuration chunk, a user would be able to select from a pull-down list of available options like: meters, centi-meters, inches, feet. In an application, the user could return something like: "return gadget::Unit::feet" This would be an alias for the actual conversion factor.

Comments

  • Why use meters as the base (internal) VR Juggler units? (why not feet, inches, centimeters, etc)

I chose meters because it is the international standard unit of measurement. It is easy for most people to use and seemed liked a better choice then the other units.

-- AllenBierbaum - 16 Sep 2002



Topic PositionalInputUnitsAndScaling . { View | Diffs | r1.3 | > | r1.2 | > | r1.1 | More }
Revision r1.1 - 16 Sep 2002 - 15:03 - AllenBierbaum
Revision r1.3 - 16 Sep 2002 - 15:21 - AllenBierbaum

Copyright © 1999-2008 by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Ideas, requests, problems regarding VRJ Wiki? Send feedback