Failure criterion state printed for CDEM

[maceligueta]

Allows printing a new result. But I need a bit of help here: the modification of the spd showing the new field should only work for CDEM, not in the general DEM.

[jginternational]

If you are using in an app a part of the xml or spd defined in another, and you want to change it without the parent app to notice, there are 2 ways:

• Fully copy: not a valid option for a small change
• Use the event [APPID]::xml::CustomTree to modify the resulting spd

For your case, change only a public name of a static parameter, the second is better.
In /apps/CDEM/xml/XmlController.tcl locate the proc CDEM::xml::CustomTree and place there something like

spdAux::SetValueOnTreeItem pn "Show bonds" BondElem ContactMeshOption

[maceligueta]

Thanks for the explanation @jginternational but how is this
spdAux::SetValueOnTreeItem pn "Show bonds" BondElem ContactMeshOption
capable of adding all this information? ->
<value n="ContactMeshOption" type="bool" values="true,false" v="false" pn="Show bonds" icon="black1" help="Calculate and show the bonds between particles"/>

Actually, I don't want to add that item. In this case, I want the bonds to be visible in all DEM guis. But when I added this piece of tree:
<value n="TypeOfFailure" type="bool" values="true,false" v="false" pn="Type of failure" icon="black1" state="[getStateFromXPathValue {string(../value[@n='ContactMeshOption']/@v)} true]" help="Displays different numbers for different types of failure. 2: tension. 4: shear or combination of stresses. 6: neighbour not found by search. 8: less bonds than minimum"/>
I want it visible only for CDEM.
Is this possible?

[jginternational]

I beg your pardon. I thought the only difference was the circled part, and I didn't see the underlined

To add a value to the spd, this is the code:

    gid_groups_conds::addF [spdAux::getRoute BondElem] value [list n TypeOfFailure pn "Type of failure" v No values {Yes,No} icon "black1" help "Displays different numbers for different types of failure. 2: tension. 4: shear or combination of stresses. 6: neighbour not found by search. 8: less bonds than minimum"]
    spdAux::SetValueOnTreeItem state {[getStateFromXPathValue {string(../value[@n='ContactMeshOption']/@v)} true]} BondElem TypeOfFailure

Note: I've splitted into 2 functions (1 for everything and the other for the 'state') to explain that each parameter can be in it's own call. You can place all the parameters in the gid_groups_conds::addF function

[maceligueta]

I pushed some changes, but they were not tested yet. @farrufat-cimne said he will take care of this.

[jginternational]

👎

[maceligueta]

ouch! That slipped in!! Will remove it immediately

[maceligueta]

Thanks for pointing out @jginternational . I think I undid it.

[maceligueta]

I recovered the Parallel configuration, which works in my machine. What type of problem was it giving on your pc, @farrufat-cimne ?
I also recovered Gravity, otherwise we can't modify its values. Please @farrufat-cimne confirm I am not making a mistake.

[maceligueta]

One more question @farrufat-cimne : it seems that we are removing fields from the tree here

GiDInterface/kratos.gid/apps/DEM/xml/XmlController.tcl

Line 31 in 68dc40c

set result_node [$root selectNodes "[spdAux::getRoute "DEMConditions"]/condition\[@n = 'DEM-Cohesive'\]"]

When the procedure should be the opposite, no? I thought the CDEM would increment the fields.
@jginternational , if we reverse the operation, adding fields in CDEM instead of removing in DEM, how can we proceed? Here we are adding one field to the tree

GiDInterface/kratos.gid/apps/CDEM/xml/XmlController.tcl

Line 34 in 16cff57

gid_groups_conds::addF [spdAux::getRoute BondElem] value [list n TypeOfFailure pn "Type of failure" v No values {Yes,No} icon "black1" help "Displays different numbers for different types of failure. 2: tension. 4: shear or combination of stresses. 6: neighbour not found by search. 8: less bonds than minimum"]

But I guess adding new conditions is different...

[jginternational]

Solved by phone.
Conditions that must only appear in the child app should not exist in the parent app, They must be loaded in a xml file in the child one

[maceligueta]

I think this is ready. I tested examples in DEM and CDEM and they run fine

[maceligueta]

@jginternational approve if you think everything is ok

[maceligueta]

I am not authorized to merge, even if it's approved...

[jginternational]

We are on Christmas ... on release period