Jump to content

Stefan Wunderlich

Moderators
  • Content Count

    85
  • Joined

  • Last visited

  • Days Won

    1

Posts posted by Stefan Wunderlich


  1. Hi Nikolas,

    There is no special CAESES distribution for windows server. The installed version should in principal run fine.

    Does CAESES (crt) starts when you run it standalone (i.e. via start menu)?

    It looks as if the environment when running caeses includes the TCAE bin directory which leads to the error (Windows resolves external libraries in this path which is wrong - at least for CAESES).
    You might try to either remove the TCAE directory from %PATH% (in the system environment) or supply CAESES with a different environment when it is started by TCAE.

    Cheers,
    Stefan

    • Upvote 1

  2. Hi Bram,

     

    Is this code snipet inside a function? We have disabled the scopewise notation inside functions due to technical reasons so you could simply write:

     

    imagecurve interpolCirccurve()

     

    interpolCirccurve.Setcurve(Curve)

    interpolCirccurve.setDomain([0.5,1])

    interpolCirccurve.setName("halfCurve")

    interpolCirccurve.SetVisible(0)

     

    Does this help?

     

    Cheers
    Stefan


  3. Hi Mohamad,

     

    There is no connection to either the geometry or the starccm setup for the used designvariables (pm1, pm2).

    So when the designengine is doing the variation, only the values change but nothing more happens.

     

    You have to modify your setup in a way that changing a designvariable leads to a changed geometry.

    Checkout the sample "S-Duct Geometry Variation".

     

    Cheers,

    Stefan


  4. Hi Hamidreza,

     

    You can use 

     

    FDesignResultsTable.countRows()

    FDesignResultsTable.countColumns()

    FDesignResultsTable.getValueAt(row, column)

     

    to access the values of a results table.

     

    something like:

     

    loop(myTable.countRows())

      int row($$i)

      loop(myTable.countColumns())

        int col($$i)

        double value(myTable.getValueAt(row, col))

        // ...

      endLoop

    endloop

     

    Cheers,

    Stefan


  5. Hi Bram,

     

    just a short note from my side:

    There is a difference between BrepSources and BooleanOperation / SolidFromIntersection.

     

    In the boolean operation, we add the source surfaces of the polysurface to increase robustness. This is maybe not in all cases the best solution and we will think this over.

    But then we would need to introduce "split continuity" in all these tools (like in BrepSources) - simplicity vs. options ;)

     

    Cheers,

    Stefan


  6. Hi Philipp,

     

    the crash is probably due to the graphics driver / hardware. In the terminal output you can see that no valid openGL context could be obtained from the system.

    We sometimes see poor driver support under Linux OS for integrated graphics (Windows too).

     

    You shoud try to find install  a prorietary / vendor driver (probably intel?) for your graphics system.

     

    An alternative could be to use a dedicated graphics card (nvidia preferable in my personal opinion). You would have vendor support and a much better performance even with a cheaper card.

    The integrated graphics is dedicated to desktop / office use, CAD is not really the idea of these things ;)

     

    Cheers,

    Stefan

    • Upvote 1

  7. Hi Harry,

     

    Have you already tried to read an IGES file exported by CAESES in NAPA? Have there been any Problems?

     

    As far as I know, all surface types are exported as type 128 and breps as trimmed surfaces. Maybe you can take a simple hull model and export it as surfaces and as well put the surfaces inside a brep and export the brep to see which works better (you can also set the tolerance at the brep but this setting might introduce problems in the brep itself).

     

    Unfortunatly I do not have NAPA, so I can't try it myself but I an most interested in the results.

     

    Cheers,

    Stefan


  8. Hi Max,

     

    You are right, CAESES can read different kind of VTK formated files (XML, legacy, ...).

    Did you try to connect via "File -> Data Connection -> VTK"?

     

    What is the error?

     

    If you could attach a small example of the kind of data to process, I can take a look into it.

     

    Cheers,

    Stefan

×
×
  • Create New...