@@ -37,4 +37,4 @@ See [Files](files) for more details about the data files generated by each of th
The design intent behind the interfaces and modular language of ViNERS is largely parallel to that of [the Rails Doctrine](https://rubyonrails.org/doctrine/). Obviously, there are differences: ViNERS is written in MATLAB, not Ruby, and ViNERS is a neural interface simulation pipeline, not a web framework, but [the Rails Doctrine](https://rubyonrails.org/doctrine/) is an excellent starting point to read to understand why certain design decisions were made.
One of the principles is that there should be many valid ways of telling the computer what you mean. For more about the different ways that ViNERS uses and interprets input arguments to most functions, see (tools.opts_to_args)[Tools/opts_to_args.m].
One of the principles is that there should be many valid ways of telling the computer what you mean. For more about the different ways that ViNERS uses and interprets input arguments to most functions, see [tools.opts_to_args](Tools/opts_to_args.m).
