Provide coherent documentation for FOMCON v1.50.x

[extall]

Currently, the biggest source of information about FOMCON, its usage, and use cases can be obtained from the following sources:

• Website https://fomcon.net/ (some tutorials are present there, as well as general information about modules, etc.)
• Miscellaneous papers about FOMCON and related items.
• Docs section on the website: https://docs.fomcon.net/ -- somewhat outdated, based on autogeneration of docs.
• My MSc thesis (contains an outdated manual for FOMCON). Download: https://a-lab.ee/edu/sites/default/files/theses/Tepljakov_MSc.pdf
• The Springer book from 2017 based on my PhD thesis: https://doi.org/10.1007/978-3-319-52950-9
• YouTube tutorial for TSP'2021: https://www.youtube.com/watch?v=cv393SzRdv8

However, a true FOMCON manual is still nonexistent. Hence, this issue. The manual ought to target v1.50.x, because of the planned changes to FOMCON v2.x.

[RICHAPRIYADARSHI]

Thankyou for the respomding sir.
I had a very trivial queries if you may consider and possible for you.
Q: while giving inputs and outputs in form of mat file, to identify a SISO system, is it necessary that both need to be in p.u. form (per unit) form. Or they may have their respective units? (Input: PV power ; Output: Busvoltages)

[extall]

The decision of which units to use (or p.u.'s) is largely up to the user and is in no way regulated by FOMCON facilities.

In fact, it might also be seen as a kind of limitation, since FOMCON's native identification object fidata does not specify units. We treat signal values just as they are, i.e., unitless abstract time series of real numbers. But attaching specific units to those may be useful indeed.

Thank you for bringing this up, I would actually submit this as a separate issue, because it is important for practical purposes to keep information about units in the data structures.

[extall]

@RICHAPRIYADARSHI I have created the corresponding issue here: #20
Feel free to suggest other fields you may want to have in case of these structures and I will consider adding them to the fidata object with the next update.

[RICHAPRIYADARSHI]

Respected sir,
I have this one question. The toolbox comes with several .m files. Where can I understand how to create my very own 1X1 fidata file ?

[extall]

Respected sir, I have this one question. The toolbox comes with several .m files. Where can I understand how to create my very own 1X1 fidata file ?

I don't fully understand the question.

.m files in Matlab are used to define functions and also for scripts. fidata is actually a class located in the @fidata folder. This makes it possible to create fidata objects in memory that hold the information necessary for the identification tools to perform parameter estimation for a given model.

So, do you want to create your fidata objects? Type help fidata or doc fidata in Matlab to learn the calling sequence. You can then store the objects in a .mat file, if you wish.

Do you want to override or extend the functionality of fidata class? Then, please refer to, e.g., https://se.mathworks.com/help/simscape/lang/subclassing-and-inheritance.html

[RICHAPRIYADARSHI]

Respected sir,
I need to create fidata object which contains mat files. Searching help fidata or doc data didn't help. ( I did that already and ended up on pages for extending fidata file in FOMCON)
I was seeking .m files in a hope they would contain coding to create fidata object.
If it is possible kindly guide me.