Welcome to the TRNSYS Users Forum.
The forum is a place where people can interact and have discussions about different topics involving the use of the TRNSYS software package. Here you can post topics for discussion or questions on using TRNSYS and get advice from other users or TRNSYS experts. This forum is not intended for detailed technical support. Users should contact their distributor’s hotline for such assistance.
Some tips for success on using the forum:
- Follow the Forum Rules posted in Forum Administration.
- There are categories for different types of topics and questions. Post your topic or question into the proper category.
- Before posting a topic or question search the existing topics (and the TRNSYS Users listserv archive or Post archive) to see if a similar topic or question has already been answered.
- Use a descriptive topic name. Don’t use attention getting subjects, they don’t get attention and only annoy people.
- State the version of TRNSYS and which add-ons your are using.
- Include enough specific details for your topic of question to be answered. Just posting “Why am I getting an error?” without describing the specific error and what you are trying to do when you get the error will not receive a response that fixes your issue.
- Remember when people help you, they are doing you a favor. Be patient, help people out by posting good descriptions of what you need help with, and be polite even if a response does not solve your issue.
- Moderators may edit your post for clarity or move your topic to a more appropriate category.
Small stuff:
- the output "day of the year" by Type 15 doesn't reset after one year.
- it would be nice if Type 9 could handle data with smaller time step than the simulation.
- it would be nice if the import from dck-file included formatting.
- a "replace" function for macros.
- in the settings, if you choose the simulation start and stop time by calendar, commas are inserted automatically which give you an error if you don't remove them.
If I could wish for anything:
- the possibility to edit multiple thermal zones at once in TRNBuild.
- TRNLizard supporting more thermal zones.
- I'd love more modularity in Simulation Studio and the possibility to define local (e.g. in macro) as well as global variables.
- errors and error messages: Sometimes I still get crashes and random errors like I need to replace a unit and then everything is fine. I guess stuff like that is hard to fix because hard to reproduce. Some error messages are great, others like the Fortran errors aren't too helpful for the non-Fortran-programmer.
- free choice of construction in the TRNBuild built in radiant floor.
- SI units (one can dream :))
Xenia, thank you for your feedback! Input like this from users is very valuable!
Can you give me a little more information about what you mean by "if you choose the simulation start and stop time by calendar, commas are inserted automatically which give you an error if you don't remove them?" That is not a behavior that I have run into or else I am not quite following what you mean by setting the start and stop time by calendar.
Also, please contact your distributor when you get those ugly Fortran errors. Those are usually cases in which the code didn't catch the actual error (like checking to make sure that an argument is positive before taking its LOG). The random crashes and need to replace a unit are, as you point out, harder to solve since they're not always repeatable. The Fortran errors can be fixed though!!
kind regards,
David
Xenia Kirschstein Topic starter
08/07/2024 7:07 am
@davidbradley
Dear David,
thanks for the Tip! I attached a screenshot which hopefully makes my meaning clearer. When I choose the 2nd of January by dropdown, commas are inserted in the simulation start and stop time. If you haven't run into it maybe it has something to do with comma being the German decimal separator (but I don't see why Trnsys should care)?
Best, Xenia
DavidBradley 08/07/2024 2:14 pm
@xenia-kirschstein
Xenia, thanks for the screenshot and yes, you're correct that it is because your computer is set to use "," as the decimal separator. Trnsys uses the "," for various things and interprets "." as the decimal separator. In this case, though, there is no reason why the interface couldn't display the "," but write the "." that Trnsys expects in the input file. Again, thanks for the suggestion.
best,
David
