Difference between revisions of "Opening a Simmetrix ticket"
From PHASTA Wiki
(One intermediate revision by the same user not shown) | |||
Line 20: | Line 20: | ||
If this is not followed, you will get an email from Simmetrix saying "Delimiter not found". | If this is not followed, you will get an email from Simmetrix saying "Delimiter not found". | ||
+ | |||
+ | SimModeler: | ||
Finally, for issues generated in SimModeler, you need to save the model with each meshing case, and then send each *.smd and *_nat.x_t, indicating which ones work and which do not. They will be able to reproduce the issue internally. | Finally, for issues generated in SimModeler, you need to save the model with each meshing case, and then send each *.smd and *_nat.x_t, indicating which ones work and which do not. They will be able to reproduce the issue internally. |
Latest revision as of 14:42, 1 December 2016
To open a ticket with simmetrix, use the following support form.
====Simmetrix Support Form==== Customer ID: jan001 Platform: linux Simmetrix Product: MeshSim Product Version: 7.2 (edit this to whichever version you are using) Type [Question,Bug,Feature Request]: Question/Bug/Feature request Priority [High,Medium,Low]: High/Medium/Low Summary: (e.g. BL gets destroyed in initial meshing at some places.) Description: Here, put a brief description of the bug or question you have for Simmetrix.
You can put the Summary above as the subject in your email. The email should be sent to "support@simmetrix.com'. Remember, for the email to get registered as a support ticket, the delimiter ( ====Simmetrix Support Form====) has to be before all the content of the email and has to be exactly
====Simmetrix Support Form====
If this is not followed, you will get an email from Simmetrix saying "Delimiter not found".
SimModeler:
Finally, for issues generated in SimModeler, you need to save the model with each meshing case, and then send each *.smd and *_nat.x_t, indicating which ones work and which do not. They will be able to reproduce the issue internally.