News: Need training? HyperSizer Training Videos are available now! Learn more here:

Recent Posts

Pages: 1 2 [3] 4 5 ... 10
By HyperSizer convention, the x-axis runs in the "a" direction, and the y-axis runs in the "b" direction. The zero stiffeners therefore run in the "a" direction as well.

So an orthogrid pocket that has S0 = 10 inches and S90 = 2 inches is long in the y-axis (b) direction because the space between 0 stiffeners is larger than S90.

I've attached the HyperSizer image of an orthogrid panel, and I've added a quick note showing where "a" and "b" are defined. Hopefully this clears things up! I think what you described is indeed the reverse of this.
I developed a non-fea project trying to optimize an orthogrid panel design for pressure loading only. I assumed from all the images I see in hypersizer that define free body and orthogrid varibles that the "a" dimension is width of panel, the x axis left to right that I match up to the S0 deg web spacing direction, while the "b" dimension of panel is height, the y axis top to bottom that I matched to S90 deg web spacing direction. I run my load case this way and get optimized orthogrid design, that looks OK in viewer. Everything is ok at this point. Then I create an equivalent ANSYS FEA model for verification and to proceed with detailed design, and it shows large negative margins in S90 web.  I  go back to hypersizser, flip my a and b dimensions only freeze all orthogrid dimensions to the optimized solution, and then rerun hypersizer, now I get negative margins in S90 web similar to ANSYS FEM.
So my question is, did I get my a and b panel dimensions mixed up with respect to S0 and S90 web dimensions? where did I go wrong?
Suggestions & Feedback / Re: Results deleted after changing Material
« Last post by JanPio on August 17, 2018, 12:55:12 AM »
Thanks for forwarding this for a possible implementation in a future release.
Would you mind to change the topic and move it to the correct subforum (if this is possible), as it is no material problem anymore? Maybe others wonder about the behavior and find the answer here.
Suggestions & Feedback / Re: Results deleted after changing Material
« Last post by Stephen on August 16, 2018, 08:00:40 AM »
Hi Jan,

It looks like you've correctly identified what happened. When "renaming" a project, a new TEMP folder is made for that project, but not populated with the old TEMP files.

This was a simplification to reduce the overhead of having to rename TEMP files (many of which are named specifically with their corresponding project name). I do understand the why this is not ideal, however. I've put in a request for our developers to evaluate possible solutions on our end.

Scripting / Re: Generating Effective and Discrete Laminates
« Last post by danvic on August 15, 2018, 11:49:15 AM »
Was this feature implemented since the last reply to this thread? Just confirming since I couldn't find this mentioned in the release notes history and current scripting documentation.

Suggestions & Feedback / Re: Results deleted after changing Material
« Last post by JanPio on August 15, 2018, 10:56:35 AM »
Hi Stephen,
sorry, the reason for deleted results was actually not the material change, which was only the last action I did before losing results.
The actual reason was renaming the project, I've just tested it again. To reproduce:
  • Sizing of a project.
  • Project Form --> Stress Reports --> Excel Spreadsheet --> Works
  • Right click on project --> Rename project --> Change name --> OK
  • Prompt to delete the folder with the old project name --> No
  • Project Form --> Stress Reports --> Excel Spreadsheet --> Message that I need to do a sizing first before creating reports
  • Close database --> renaming old project folder to match new name --> open database again --> Still no report possible to create

So for future releases, is it possible to keep all the features when renaming a project?
Workaround: renaming the project back to the old name brought back the stress report, but I guess only if I do not confirm to delete the old folder (which I always did, expecting the new project folder holds all the information needed for reports).

Miscellaneous Software Topics / Compact Database - Assembly Project Manager
« Last post by martinjb on August 14, 2018, 11:35:03 AM »
I have recently been investigating the Assembly Project Manager and how it could be implemented within our processes.

My initial database has a file size in the order of 500,000kb.

If i create a set of 5 assembly projects at a major assembly level (front/rear fuse, wing etc.) i get databases that are the same size as the original (500,000kb) and therefore 5 x 500Mb = 2.5Gb of disk space used.

If use the button Add Project per Assembly in the Assembly Project Manager and i have 40 assemblies the total disk spce that i have used is 20Gb.

Looking at the 5 new assembly projects that i created at the major assembly level, if I go into each database and compact them, I reduce the total disk space to 183Mb.

Is this the only way to ensure that the minimum space is taken on the disk, by compacting individual databases or is there a toggle/backdoor switch that compacts a database automatically as it is being created?

Also when compacting a database what is being compacted/removed?  Is it all the designs that haven't met the defined criteria being removed?  What would you say is the correct practice for compacting a database?  After each run? Over a certain size? Or ....

Sorry if there are too many questions in one post


Sometimes you import a model with 1 or more sections, but you want to include more components.

There are two ways to do it: update your input file with more components
Or use the FEM viewer (create components using FEM Viewer (by element))

But when you have a model with 1000 elements the second option is nearly impossible.

It would be nice if you could select by surface angle or other options.

Suggestions & Feedback / Re: Results deleted after changing Material
« Last post by Stephen on August 10, 2018, 09:02:13 AM »

I'm a little confused about the behavior you're describing. Are you saying that making a change in the sizing form and saving has caused the TEMP files to be deleted for that project? That would be very surprising, so if it is repeatable we would want to address that.

Regardless of the cause, if the TEMP files for the project are gone, the only way to generate reports is to analyze the project (or relevant assemblies) again.

A limited amount of results (such as minimum margins of safety) is stored in the database, which is why you are able to see some of this data. But the majority of the information needed to generate reports lives in the TEMP files.

Hope this helps,
Pages: 1 2 [3] 4 5 ... 10