#305 Raytrace of v4 database on version 7.20.0

closed-fixed
Raytrace (49)
7
2011-11-16
2011-08-31
No

When raytracing a v4 database on Microsoft Windows XP & 7 with vversion 7.20.0, the partition structure returned by the hit function does not have the pt_regionp data filled in correctly. This can be fixed by upgrading the database.

Discussion

  • Sean Morrison

    Sean Morrison - 2011-09-02

    Thanks for the report, but a few follow-up questions:

    How did you ascertain that the pt_regionp data was not filled out correctly?

    Was the v4 file created on a little or big endian platform?

    Did you perform the dbupgrade on that same Windows system or on a different system? If different, was it big or little endian?

    There is now code that reads in (incompatible) v4 files, but there are several potential "gotchas" given the uncertainty inherent in the data.

     
  • Sean Morrison

    Sean Morrison - 2011-09-02
    • assigned_to: nobody --> brlcad
    • milestone: --> other bug / workaround
    • status: open --> pending
     
  • Christopher Pitts

    • status: pending --> open
     
  • Christopher Pitts

    How did you ascertain that the pt_regionp data was not filled out correctly?
    We have codes that use various data out of the structure and the values are always 0 in 7.20.0. It worked fine in 7.12.2.

    Was the v4 file created on a little or big endian platform?
    It was created on a little endian platform from an ascii file several years ago.

    Did you perform the dbupgrade on that same Windows system or on a different system? If different, was it big or little endian?
    Same machine.

     
  • Christopher Pitts

    I have tracked this to the db5_sync_attr_to_comb (db5_types.c) function called from db_recurse (db_tree.c) is resetting the comb structure when a version 4 database is opened.

     
  • Sean Morrison

    Sean Morrison - 2011-11-15

    That was indeed related to the problem, but only half the picture. A fix was applied, however, that should get things working again. If you would, please test with a current checkout?

     
  • Sean Morrison

    Sean Morrison - 2011-11-15
    • assigned_to: brlcad --> tbrowder2
    • priority: 5 --> 7
    • status: open --> pending-fixed
     
  • Christopher Pitts

    The patch fixed the problem.

     
  • Sean Morrison

    Sean Morrison - 2011-11-15
    • assigned_to: tbrowder2 --> d_rossberg
     
  • Sean Morrison

    Sean Morrison - 2011-11-15

    Outstanding! Sorry it took so long to fix, but thanks for testing Chris. A lot of testing went into making sure v5 wasn't affected, but there is no regression testing for v4 data. Is there a particular reason dbupgrade hasn't been run on that geometry?

    Barely related, your name is included in our release credits for the upcoming release for pinpointing the g-obj bug. Just an FYI.

    Cheers!

     
  • Christopher Pitts

    We had not got around to upgrading every geometry we had. We have since went through and upgraded all of them to v5.

     
  • Sean Morrison

    Sean Morrison - 2011-11-16

    Understandable, thanks for the info. Thanks again for the reports and debugging too. Extremely helpful. Cheers!

     
  • Sean Morrison

    Sean Morrison - 2011-11-16
    • status: pending-fixed --> closed-fixed
     

Get latest updates about Open Source Projects, Conferences and News.

Sign up for the SourceForge newsletter:





No, thanks