Web manual documentation update issue → The manual will be updated until 0000
Not implemented Essential Components during Testing
Function | Explanation |
|---|---|
Units | → Civil has presetting unit when the user opens a new file. In this case, the user needs the “Patch” method to change the current mode given unit. |
Concurrent (Max/Min) Reaction | → Developing until the end of this year |
View by Max value Item | → Developing until the end of this year |
Tapered: Composite Sections | → Developing until the end of this year |
Python Client
Function | Findings | Explanation |
|---|---|---|
Units | → Key value of “1” already existed | → Civil has presetting unit when the user opens a new file. In this case, the user needs the “Patch” method to change the current mode given unit. |
Material Properties - URI & JSON confusing | → URI & JSON body is not clear | .png?version=1&modificationDate=1661243789271&cacheVersion=1&api=v2) This is the new web communication method example. This method has already been included in the header(In the URI). You need to change the first line of JSON to “Assign.” Here’s the new manual. [MATL] Material Properties - MIDAS API - MIDAS-Support (atlassian.net) I’m sorry for the confusion. Revision 1 manual was written based on the window command method, so the new way of the URI and JSON were changed. Of course, we are preparing a new manual for beta usesuse. Please wait for it. |
TDMP: Material Link | → TDMT_NAME, TDME_NAME unclear | .png?version=1&modificationDate=1661299242950&cacheVersion=1&api=v2) The manual consists of Common items and Code Specifications. You can find out more information in the Code Specification part. Here are updated manual: [TDMT] Creep/Shrinkage - MIDAS API - MIDAS-Support (atlassian.net) |
TDMP: Change Property - Decimal problem | H_VS input values are being rounded incosistently to 2 decimal places | .png?version=1&modificationDate=1661301649569&cacheVersion=1&api=v2) You can set a rounded decimal point in the element dependent material property tap.  |
SP: DB/User: I | → H/I Section confusing → OFFSET options are not clear | .png?version=1&modificationDate=1661319434892&cacheVersion=1&api=v2) I’m sorry for confusingthe confusion, I found out that the US version and Korean version versions use the different name abounames of I-Beam and H-Beam. |
SP: Composite: Steel-I | → Order of section dimensions are not clear | The vSize order is just same as the Civil UI, and please look over our manual for offset parameters. [SECT] Common Items (Section data & Offset) - MIDAS API - MIDAS-Support (atlassian.net) |
Supports | → Boundary group needs to be created before the supports → Constraint sequence | Boundary Group and Constraint 0,1 arrangement are the same as when you used Civil. Basically, you need to create a boundary group before you create supports in the civil, and when you set support up on your node, you can check 111111(all fixed) on your mct. These are just the same! [CONS] Define Supports - MIDAS API - MIDAS-Support (atlassian.net) |
Traffic Line Lanes | → “Name of Load Group” → “Structure Group” | Thank you for your findings! We updated to a latest manual, please check it! |
Vehicles | → no links between manuals (Moving Load - Eurocode and Vehicles) | → We already have awarded that we need links between them. This is a temporal manual, so some of reasons we couldn’t create links. Please understand it. When we release official version of Civil API and manual we definitely consider their availiability. |
Moving Load Cases | → As same as above | → We will offer nevigator with official manual! |
Composite Section for Construction Stage | → JSON code not defined all Key in document | → We will offer nevigator with official manual! |
Load Combinations | → Missing CS and MV in manual | → We just needed manual update! We already have CS and MV. Please check our latest manual! |
Reaction | → Need clear analysis type next to the load case/ combination name | → Developing….! |
Concurrent (Max/Min) Reaction | → Not found | → Developing….! |
Beam: Force & Stress | → Need to be seperated | → We offer seperated Force & Stress Tables |
Beam: Force - View by Max Value Item | → Not found | → Developing….! |
Composite: Steel box | → Need clarity of order of section parameters | → We will offer specific Section parameter manual |
Composite: Tapered | → Not found | → We are making a new example now, please wait for it. |
Settlement Concurrent Reaction Group | → This documentation should be located in <Load> Settlement Section → Not clear that the Groups key is the structural groups | → Updated with additional details [CRGR] Concurrent Reaction Group - MIDAS API - MIDAS-Support (atlassian.net) |
Analysis Control: Settlement Analysis | → Required CONCURRENT_CALC and CONCURRENT_LINK clarity → typo “??” | → “??” is kinda of typo it is 🔺 [SMCT] Settlement Analysis Control Data - MIDAS API - MIDAS-Support (atlassian.net) |
Model View Screenshot | → Not found | → Developing…! |
Screenshot at Construction Stage | → Not found | → We consider to show deformed and undeformed shape for screenshot now, it will be updated soon! |