News: Contact us to upgrade your software!

Recent Posts

Pages: [1] 2 3 ... 10
Hi Gawain,

Make sure the "Geometry Check Rule 4" failure mode is activated in the sizing form, failure criteria tab for the applicable components. It should be contained in the geometry check category.

Analyzing & Optimizing Stiffened Panels / Orthogrid Stiffener Height to Thickness Ratio
« Last post by Gawain on January 16, 2019, 11:59:56 AM »
Is there a way to set the maximum stiffener height to stiffener thickness ratio?  I've gone through the backdoor data and in 'Geometry Checks', I've changed Rule 4 which I think should do this but doesn't seems to work.  Is this the correct setting to change and if so, should it work for a Orthogrid panel concept or is there an alternative way of doing this?
Most likely the easiest way to accomplish this is through the scripting API. You can write a script (in VBA, Python, C#, etc.) that extracts the results for all designs of components. For this, use the Component.ResultVariable() method:

You can see that it accepts the variable ID in question (corresponding to e.g. the skin, spacing, etc.), and optionally a solution ID. You'd need to have the script loop over the variables of concern in addition to looping through the solutions available.

Within a component optimisation process, you can ask hypersizer to show you the top 10 or 100 etc designs for that component during a detailed sizing operation.  Is there a way for this data to be outputted into a spreadsheet or similar format? 

At the moment all I can find is the information within the .AOP file, but this does not seem to output the skin thickness, web thickness, stiffener height, weight etc for each design.  Is there any way to output this information for all designs required?
Miscellaneous Software Topics / Re: Nastran HDF5
« Last post by martinjb on January 11, 2019, 04:20:56 AM »
Thank you
Miscellaneous Software Topics / Re: Nastran HDF5
« Last post by James on January 10, 2019, 08:33:46 AM »
We've had many conversations about it internally. However, it's not on the immediate (3-6 month) development plan. I believe we'll revisit it again after 6 months.

Miscellaneous Software Topics / Nastran HDF5
« Last post by martinjb on January 10, 2019, 08:29:40 AM »
Dear Hypersizer,

Is there any view/roadmap on Hypersizer integrating the HDF5 results into the software?

Scripting / Re: COM access to the Update FEM Process that preserves dat structure
« Last post by August on December 13, 2018, 09:07:22 AM »

HyperFEA is actually using the HS API to run, so the output FEM will be the same format between HyperFEA and the API Project.UpdateFEM method, as you identified.

At this time, there is no other FEM update method in the API. This would be a useful feature and we would consider adding it in the future.

Scripting / COM access to the Update FEM Process that preserves dat structure
« Last post by danvic on December 12, 2018, 05:39:14 PM »
As stated in the Hypersizer manual:

The FEM update process for Nastran is different from the iteration FEM process. In FEM update the goal is to preserve the original structure of the source FEM as much as possible (in HyperFEA the goal is to rapidly generate a new FEM to get an updated load path).

The Hyper FEA type of FEM update is covered by the Project.UpdateFEM method - is there a class/method exposing the other type of FEM update that preserves the Nastran dat file structure?

Miscellaneous Analysis & Methods / Re: Reading Initial Temperature from NASTRAN deck
« Last post by Brent on November 29, 2018, 09:56:51 AM »
Hi Ruben,

The reference temperatures defined on the load sets are not imported from the FEM. These values are specified by the user.

In order for HyperSizer to import the applied and initial temperature(s) defined in the FEM, the reference temperatures assigned to the HyperSizer loads sets needs to be set at room temperature (22.22222 Celsius). If there are no thermal subcases defined in the FEM, HyperSizer will not import an initial temperature "TEMPD".

Also, when more than one thermal subcase is defined in a rundeck, HyperSizer will not read the initial or applied temperatures in the FEM. Therefore, it is best practice to create unique rundecks for each thermal subcase. This way, the unique thermal case temperature dependent material properties can be updated to each FEM.

When you only need to define a single reference temperature per subcase, I recommend to modify these values for each load set in HyperSizer spreadsheet.

Hope this helps!


Pages: [1] 2 3 ... 10