It would save substantial time and reduce human error if we had the ability to create either input files, or input lines within Precede. The various input files have different input formats (e.g., some need spaces, some do not have spaces, etc.). It would be a huge advantage if all this could be done using Precede and a text file created in the proper format for the indicated input file type.

For example, to be able to create a joint can input file or the input lines (ex. JMOD, BRCOVR) in the proper format would save a lot of time. The define list works moderately well for this with the work around to reformat the lines to match the proper input format. However, there are other input lines for other input files that are more complicated and time consuming.

I am currently using the BSSEL input in a collapse input file. This input requires member end joints and a joint to define as the chord joint. If I could create these input lines using Precede it would be much faster and would reduce the likelihood of input errors (typo’s).

Some other good examples are; brace/chord overrides and joint selection for fatigue input files.

Additionally, any files that are created outside the main input file often get out of sync, especially with joint names and member names if they change. It would be quite helpful in reducing errors and saving time if the files could be linked or embedded in some way so that updates (such as changing a joint name) ran through all the associated files.