Here are the ways to get help and/or lend a hand:
Browse the online documentation at https://docs.gridlabd.us/. The answer to most software usage questions are found there. If the command you are looking for isn't listed or isn't described correctly/sufficiently, then you should probably create a ticket.
One common technique for starting a new project is to find a validation test for your use-case. If you know which module you should be using, you can browse the modules for an autotest file that validates the system for your problem. Test files are named test_*.glm, where the name corresponds to the validation use-case. There are about 750 validation tests which cover just about every use-case imagined for HiPAS GridLAB-D.
If a command is not working as expected or as documented, then you should submit a new problem report describing the problem. Be sure to search the existing issues first to see whether it has already been reported. If not, please provide an explanation of how to repeat the problem with the simplest possible example you can come up with.
If you need a new feature, then you should submit a new enhancement request. Be sure to search the existing issues first to see whether it has already been requested. If not, please provide as much information as you can about the purpose of the enhancement and how it might be implemented.
Do you have a general question for the user community? Please use the discussions page to post your question in the appropriate category. You can also send an email to arras-discussion@lists.lfenergy.org. For sensitive topics, please use arras-private@lists.lfenergy.org. A channel on Slack can be reached using #arras.
If you think you have found a security vulnerability, please email the information to email:security@arras.energy.
Please refer to CONTRIBUTING.md to make a project contribution.