Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Already on GitHub? Sign in to your account

Range scanning/display features #2

Merged
merged 5 commits into from Feb 29, 2012

Conversation

Projects
None yet
2 participants
Contributor

petermoz commented Feb 29, 2012

As a result of our email discussion, I've packaged the "new" features as this separate branch...

  • Scans are added with their "frame number".. eg Scan.0, Scan.10 etc..
  • Scans display only in the relevant frame (e.g. Scan.10 is visible only in frame 10)
  • When doing a "scan range", scans will be added if that option is selected
  • The delete operator deletes all scans (and "noisy scans") in the scene
  • If "Sensor Coordinates" is selected:
    • File data is output in sensor frame
    • The matrix_world of the blender object is modified so it displays in the right place
  • If "Sensor Coordinates" is not selected:
    • File data is output in world frame
    • Blender object is inserted at the origin

petermoz added some commits Feb 29, 2012

@petermoz petermoz BugFix: Scene and Blendodyne FPS/timestamp issues
Blendodyne was not making correct use of the sensor rotation
speed and scene FPS settings
fe42f4a
@petermoz petermoz Operator to delete generated scans from scene
Also, changed scan names to CamelCase (as per blender convention)
and added a frame number to each scan.
ef0bae0
@petermoz petermoz Created scans are now only visible in the corresponding frame d07508b
@petermoz petermoz Allowed scan range to add scans to scene 323240a
@petermoz petermoz Display scans in world coordinates
Scans that are saved in the sensor frame are transformed in the
scene so that they appear in the correct location
074df1d

@mgschwan mgschwan added a commit that referenced this pull request Feb 29, 2012

@mgschwan mgschwan Merge pull request #2 from petermoz/experimental
Range scanning/display features
c704cc4

@mgschwan mgschwan merged commit c704cc4 into mgschwan:master Feb 29, 2012

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment