Welcome to the Altair HyperWorks How-to channel. This is your comprehensive resource for navigating Altair’s design and simulation and digital twin platform. Here, you'll find everything from product launches and updates to workflows and webinar recordings. We cover topics such as structures, motion, fluids, thermal dynamics, electromagnetics, electronics, controls, and embedded systems.
Please note that this channel is not a substitute for our online help, product training, customer support, or community engagement. For customer support and community engagement, please visit community.altair.com/community. For all other information, visit www.altair.com/.
**Altair and its subsidiaries are not responsible or liable for the accuracy or completeness of the content, or the explanations and representations in the video sequences.**
I don't see this being a benefit in a large model. (1e6+ elements). In big models you aren't going to model, let alone mesh, individual fastener holes enough times for this to be useful en masse. I'd rather see a tool to help clean up bad fasteners (e.g. NASTRAN rbe3 and rbe2 elements, and replace them with 1D elements or RBARs with mesh refinement).
Hello, this data can not be exported directly to CSV, but you can list the sensor data, just like call out table, and then copy paste in excel. I would suggest for future technical questions, to reach us on the Altair Community for the fastest response: community.altair.com/community?id=csm_get_help&sys_id=de45c412c312310015519f2974d3ae1b
hello @Robertkuepper4214, which issue are you facing with this video? We hear clearly the speaker from our side, could that be a setting issue from your side? Or is it about the speaker tone/wording/accent?
Dear Mr. thank you for your very good explanation . i need explanation about cubesat and quadrifilar helix antenna please. again, thank you very muchgain thank you very much
it's really stupid to change the interface 💩you say that new users were hard to learn and you forget the effort we made to get there! in the end we will use patran
hello @yvescartier7884, thanks for your honest message. We understand this change can cause some frustration, that should not prevent our frustrated users to contact us and to communicate in a polite and professional manner. If you consider you are loosing efficiency and time , please report it to Altair so that we can support you in this transition and make sure you can not only recover your previous process time but also get some extra gain with time to deliver challenges
Thank you for this. You mention that for the Welch method, the number of segments is equal to the signal length divided by the window length. And you then write a version of this statement in your code defining WindowLength. However, since the Welch method overlaps segments, would it not be the case that if you had a window length of 1/10 length(s) with 50% overlap, in order to cover the full length signal pWelch would need to create 19 segments, since each additional segment covers 1/5 more of the signal? Also, is the psdapp included in the Compose personal edition?
hello @andrewrutherford568, please feel free to submit a support request so that we can support you and understand why you are not able to reproduce the steps described in the video
How to loop over different types of results, like displacement, stresses, strains, etc all at once. As of now only the selected results are getting looped.
hello @ananthansp, looping over results is not available (yet). With the Python automation we started to introduce with 2023, our plan is to make it available and to offer more flexibility. We still have some milestones before delivering such feature, so stay tuned :)
Hi there, if you install S-FRAME on the same machine as Revit, the plugin should be installed automatically. If you have tried this, and still have issues, please reach out to our support team here: community.altair.com/csm?id=csm_get_help&sys_id=de45c412c312310015519f2974d3ae1b
Congratulations Altair! In one shot you have ruined one of best meshing software ever! No one cares about fancy logos, icons, aesthetics other than your software UI team. New version is absolutely pathetic without old menu, options, shortcuts and mouse operations (Especially for those who work on complex models). It is just a repackages garbage. No serious old user will switch to this crap. Listen to your customers and bring back old HM options/menus/mouse operations. You can't expects thousands of existing engineers learn new GUI for sake of marginal improvement (Shortscuts and operations are imprinted into muscle memory after years of work) If Microsoft couldn't force people to switch new GUI in their windows software, what makes you think Altair with limited users and use case can dictate the market ?? its a brain fart decision whoever made it! Rant over..
Hello @Sunilarkt, thanks for honest and passionate feedback. You are speaking about muscle memory. That is probably one of the single reason that would force a software company (or any company) to keep the way of doing things because "this is the way we've doing it for many years". Point is, no product (either software or hardware) offers the same user experience than 10-15 years ago. Or such product get replaced because other companies propose disruptive (and generally) more efficient methods. We needed these changes for many reasons (consistency across products, most efficient development of cross utilities, competition, AI integration...) and we are always willing to expose to our users why we brought these disruptive changes and the benefit they can bring to our users. If you have some metrics showing you are not able yet to achieve similarly with the new UI the tasks you are performing on a daily basis, please reach us out through regular support channel or your local representative, so that we can support you and expose you the best strategies with our latest versions.
Why does this " node path beam elements" not exist anymore in Hypermesh 2023? If you deal with LS-DYNA its a must have to create Nullbeams for contact.
hello @stefanindahouse8458, thanks for reporting us this use case. Does that mean you do not use *CONTACT_AUTOMATIC_GENERAL, or *CONTACT_AUTOMATIC_GENERAL_INTERIOR and that you crete a 1D mesh along all your shell edges?
@altairhowto With all due respect, at least for me this was not the best move, a bit too bold to call it a bold move. As a user of Altair tools, I lose productivity with this eye candy update. Altair should have at least allowed for the option to keep the panel view setup. Ask your users if it really "improved overall user experience". Just reading through the comments here, it seems I'm not alone.
Hello @gustavoguimaraes7475, thanks for your honest feedback. We have communicated for many versions that panels were going to be removed. In few words, the learning slope for fresh users was complex (any HyperMesh trainer got the same feedbacks at the end of training) and the design of interface lead to unnecessary clicks/mouse travels. Users starting with the new UI can now learn HyperMesh basics more easily. That said, these changes are significant for our historical users and we are supporting them to transition. If you think a web meeting with our teams can help, please feel free to contact us through the support channel
Nice tutorial. I had a question. What do those frequencies mean for fixed free and free free analysis respectively? Are they the natural frequencies of the system of free free?
Free-Free analysis is modal analysis without any constraints. Generally done to check your connections. First few modes of free-free is almost or near to 0Hz. Yes those are the systems natural frequencies.
Yes you heard that right, your government thinks you are the equalivant of salt water. Criminal that FCC doesn't require that CELL BIOLOGY isn't tested/observed to see what these microwaves are doing to our bodies ...many things happen BELOW the thermal increase...like blood brain barrier being OPENED UP for example.
hello @mustafatugberkcakr3364, the Field feature does not allow yet nodal thickness mapping. As a work-around, you can map elemental thickness then switch to nodal thickness: ru-vid.com/video/%D0%B2%D0%B8%D0%B4%D0%B5%D0%BE-DREssGFSPBU.htmlsi=83mbSTh55uqPkBQN If you are interested by this feature, please create a support request so that we can track your demand properly. Also, if you have access to the orignal CAD, you can use the Map Thickness method directly, which proposes the different mapping method: ru-vid.com/video/%D0%B2%D0%B8%D0%B4%D0%B5%D0%BE-RRfn_GqUELk.htmlsi=5KRYUWCUy6GzredW
I want to simulate the condition that array antenna be put by an iron door, the array antenna diffract the EM wave and I want to observe the diffracted field. Can Feko make it?
Thanks for the video. But where Can I find the Tool option from the panel. I am using at home office Hypermesh 2022 with classical Panel whereas Hypermesh 2023 without classical panel. Now I saved some file using 2023 and when opnes in 2022 it is not showing panels. I need to know how to get tools for eqivalence, duplicate nodes etc from tool option. Thank you in advance
hello @sanjaip.s8429, we have integrated from the first release of the new interface a search tool top right which allows to fill in any legacy command (such as equivalence, ...), and to get as output the equivalent command/location in the new interface. Also, the different tools you are mentioning are related to model validation, and are now available from a unique ribbon Validation. For instance, duplicate elements will now be under Model Checker. Hope that helps!
hello @Ferdy1979, the extension file and Notepad++ template should be released i the coming days. The VS Code extension is already available on the marketplace HyperWorksPyAPI - Visual Studio Marketplace: marketplace.visualstudio.com/items?itemName=AltairEngineering.hwapi-python
