|
[Sponsors] |
![]() |
![]() |
#1 |
New Member
Sarath
Join Date: Mar 2017
Location: Spain
Posts: 21
Rep Power: 7 ![]() |
Hello All,
How can we use foamDictionary with topoSetDict and access the keywords inside actions() ? I understand that 'actions' is a list of dictionaries. Is there any way to access/modify the keywords inside the dictionary actions? I tried, Code:
foamDictionary system/topoSetDict -entry actions.entry0 -value But with the dictionary constant/polyMesh/boundary which has similar structure as topoSetDict, foamDictionary works without any problem. Can anyone here help me understand this? Thanks in advance |
|
![]() |
![]() |
![]() |
![]() |
#2 |
New Member
Marius
Join Date: Aug 2020
Location: Germany
Posts: 6
Rep Power: 3 ![]() |
Hi,
I'm currently looking into this exact problem. The main difference I see when comparing the boundary file to topoSetDict: boundary contains a list of labeled subdicts whereas topoSetDict contains the actions keyword containing a list of unlabeled subdicts. foamDictionary uses labels to reference the entries, therefore you can't reference an individual entry in the actions list My current solution is using a bash script to generate or modify the complete entry I want to assign to actions as a string and then setting it with Code:
foamDictionary -entry actions -set"($ACTIONS)" system/topoSetDict |
|
![]() |
![]() |
![]() |
![]() |
#3 | |
Senior Member
Mark Olesen
Join Date: Mar 2009
Location: https://olesenm.github.io/
Posts: 1,447
Rep Power: 35 ![]() ![]() |
Quote:
This is correct, but already added in some initial work to support named dictionary entries as a first step to supporting 'actions' as a set of dictionaries instead. Needs more work, but this similar to why the "functions" entry (for functionObjects) changed from "functions ( ... )" to "functions { ... }" - to allow dictionary manipulation. Just hasn't been enough pressure to change topoSetDict as well. |
||
![]() |
![]() |
![]() |
Thread Tools | Search this Thread |
Display Modes | |
|
|
![]() |
||||
Thread | Thread Starter | Forum | Replies | Last Post |
[snappyHexMesh] snappyHexMesh error "Cannot determine normal vector from patches." | lethu | OpenFOAM Meshing & Mesh Conversion | 1 | June 3, 2020 07:49 |
Problem in topoSetDict (Unique Error) | Raza Javed | OpenFOAM Running, Solving & CFD | 3 | May 4, 2019 02:34 |
[OpenFOAM.com] OpenFOAMv1806 with amd aocc 1.2 / 1.3 compiler | cfdx | OpenFOAM Installation | 10 | February 27, 2019 04:59 |
Fatal error: invalid wall function specification | kcc49 | OpenFOAM Running, Solving & CFD | 13 | September 26, 2018 04:07 |
chtMultiRegionSimpleFoam: crash on parallel run | student666 | OpenFOAM Running, Solving & CFD | 3 | April 20, 2017 11:05 |