[brlcad-tracker] [ brlcad-Bugs-1609274 ] region id limit

View: New views
1 Messages — Rating Filter:   Alert me  

[brlcad-tracker] [ brlcad-Bugs-1609274 ] region id limit

by SourceForge.net :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

Bugs item #1609274, was opened at 2006-12-05 15:02
Message generated for change (Comment added) made by brlcad
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=640802&aid=1609274&group_id=105292

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: Analysis
Group: unexpected behavior
Status: Closed
Resolution: Invalid
Priority: 7
Private: No
Submitted By: Dwayne (dwaynelk)
Assigned to: Cliff Yapp (starseeker)
Summary: region id limit

Initial Comment:
There appears to be a bug in BRL-CAD which limits region ID numbers to around 32,000.  The limit should fixed to facilitate mulitiple vehicles in force-on-force applications.

----------------------------------------------------------------------

>Comment By: Sean Morrison (brlcad)
Date: 2008-08-22 21:52

Message:
Logged In: YES
user_id=785737
Originator: NO

And as a follow-up, the behavior of reid was changed to recognize regions
that are multiply referenced in a given hierarchy any only increment their
region ID once so that there will not be gaps in the region IDs that get
assigned.  This was applied as commit r32508 and should be in the next full
release of BRL-CAD.

----------------------------------------------------------------------

Comment By: Cliff Yapp (starseeker)
Date: 2008-08-22 20:37

Message:
Logged In: YES
user_id=11463
Originator: NO

After investigating the model/machine that triggered the bug report, the
problem was found to be unexpected behavior of running the reid command on
a tree structure with multiple references to regions in different
sub-trees.  The region incrementing while walking down the tree was
resulting in the multiply referenced regions getting multiple increments
due to reid not recognizing it had already incremented a given region in a
previous reference.  This caused unexpected "jumps" in region_id looking at
the original tree.

Closing this particular bug as this is not a region_id limit issue -
either improving geometry arrangement or using reid on sub-trees that don't
reference another high level tree will work.

----------------------------------------------------------------------

Comment By: Cliff Yapp (starseeker)
Date: 2008-08-22 03:01

Message:
Logged In: YES
user_id=11463
Originator: NO

reid was thought to trigger the limit, but tests out on OSX.  This REALLY
looks like it is a consequence of V4 database format - can anyone supply a
way to trigger this with a V5 database?

----------------------------------------------------------------------

Comment By: Cliff Yapp (starseeker)
Date: 2008-06-30 17:44

Message:
Logged In: YES
user_id=11463
Originator: NO

Tweaked insertion to add region IDs, doesn't seem to impact MGED, nirt or
rt.



File Added: stresstest.c

----------------------------------------------------------------------

Comment By: Cliff Yapp (starseeker)
Date: 2008-06-30 16:46

Message:
Logged In: YES
user_id=11463
Originator: NO

Wrote a proc-db to generate 33000 regions with one sphere each in them
(see attached.)  NIRT reports all of them, and MGED seems to be able to
load, draw and raytrace (rather slowly, obviously).  Dwayne, what's a good
way to trigger the bug?
File Added: stresstest.c

----------------------------------------------------------------------

Comment By: Sean Morrison (brlcad)
Date: 2007-02-08 22:35

Message:
Logged In: YES
user_id=785737
Originator: NO

dwayne, what tool were you running into the region ID limit on?  mged, rt,
nirt, or something else?

----------------------------------------------------------------------

Comment By: Lee Butler (lbutler)
Date: 2007-01-22 19:19

Message:
Logged In: YES
user_id=1179270
Originator: NO

Let me guess: The limit is about 32767 right?  That's the size of a 16 bit
signed integer.

In the V4 database format, the regionID was limited to 16bits.  So on V4
databases, you are stuck.  Now on a V5 database, it is less clear.  A
cursory look at the code did not make it obvious if there was a hard limit
in the database format.  We need to dig further.

----------------------------------------------------------------------

You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=640802&aid=1609274&group_id=105292

-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
BRL-CAD Tracker mailing list
brlcad-tracker@...
https://lists.sourceforge.net/lists/listinfo/brlcad-tracker
LightInTheBox - Buy quality products at wholesale price!