Hi, I´m making some tests and would need to remove the *Heading card of the model, but cannot do it using the keyword editor as far as I know.
Keyword editor can’t edit or remove existing keywords. So the only way for now is to export the input file and edit it outside of PrePoMax.
Alternatively, you could comment out these lines in CaeModel --> FileInOut --> Output --> Calculix --> CalculixFileWriter.cs and recompile:
Compilation is really easy.
1 Like
If you hate it in the results, you can do the following.
After the analysis completes, do not open the results in PrePoMax.
- Use a text editor and open the results file .frd
- Delete/change the 2nd line of the file and save.
- Then open the results in PrePoMax.
I´m testing another solver that has some similarities with CalculiXAbaqus, but *HEADING card is not supported, so it makes me run the models from command line. If that card would be removed the solver would run directly from PrePoMax gui and the results imported directly as it would be CCX.
Probably a new feature to remove some existing card would be usefull.
In the past, there was a discussion about allowing existing keyword edits and removals in the Keyword Editor. It would be very useful, but of course it’s also risky as you can easily break your model this way. Perhaps it should still be left for the user’s respoinsibility, though. In Abaqus, special *Conflicts cards are added and the user may easily discard individual or all edits with a single button.
If you edit a keyword using the Keywords Editor and then use Abaqus/CAE to make a change to your model that refers to the same keyword, Abaqus/CAE cannot determine which version of the keyword to incorporate in the input file and writes text to the input file signaling the problem. As a result, an error is generated when you submit the model for analysis. If you display the input file using the Keywords Editor, any keywords or data lines that conflict are indicated by a *Conflicts statement. In addition, the *Conflicts statement indicates whether the text was generated by Abaqus/CAE or by the Keywords Editor. You should use the Keywords Editor to remove any unwanted keywords or data lines. You should also remove all the *Conflicts statements.
1 Like
Add an option:
If other solver, not export *heading
This option is needed if want to support the other solver.
I will look into the general solution that enables modifying keywords. If I can find it. In the other case, I will try to find more specific solutions.
1 Like
Yeah, I think that a general way to edit/remove keywords would be better. After all, other cards may not be supported by this (or other) solver as well and keyword modifications can be helpful for various reasons.
In my opinion, if I may offer a hint, keyword removal is only used by experts (which I am not). Therefore, this option should be hidden in the program’s options with a clear warning. It shouldn’t be available in the keyword editor, so it can’t be accidentally used. Since the program already has the option to deactivate and set keywords as comments, a single control is enough. Once enabled, the entire editor is unlocked, allowing anyone to insert the “**” symbol and change the text color.
Above, I showed how it works in Abaqus. For less advanced users, there could be a simple switch. But ultimately, many users may need full keyword editing/removal functionality. Of course, it doesn’t have to be implemented on this occasion, it might be a separate topic.
The problem with a simple solution is that once activated, the edited content takes over the .inp output. So any following changes in the GUI must not be allowed, or they will introduce content clashes. The solution must handle changes in the Keywords editor and in the GUI at the same time, and detect change clashes on a local level, one keyword.
1 Like
Maybe instead of the keyword editor, support for FEMaster could be limited to conversion, like for Abaqus input decks.
By the way, the FEMaster´s author has introduced support for the *HEADING card in the last releases so is not more a concern.
Right, the register_heading.inl file among the supported cards: FEMaster/src/io/reader/commands at master · Luecx/FEMaster · GitHub
Ok, I found a way that did not require changing all the code (AI). Now it is possible to change/disable all keywords in the Keywords editor that are not title keywords (only comments).
Once a keyword is changed, it can be reset.
All added and modified keywords are shown in the tree using the blue font and are separated by an icon.
After the editor closes, the modified keywords are checked for the changes in the GUI. If a change is made in the GUI that affects the modified keyword, the change is first accepted, the modified keyword is reset, and the user is notified that it happened. Unfortunately, the check is much easier after the change is made, so I implemented it this way. I think it will suffice for most edits.
1 Like
By title keywords do you mean the green sections created by PrePoMax (such as e.g. “Node sets”) ?
Great ! So it’s something like what Abaqus does expect that you don’t have to remove the *Conflicts blocks manually.
Yes, those are title blocks.
And keywords containing … hidden data … can only be changed when hiding is disabled.
1 Like