Add autogen for AMDC article in control with AMDC folder

[Daehoon-Sung]

This is to close #143 to close #149 to close https://github.com/Severson-Group/AMDC-Examples/issues/6.

Notes

This comment might be useful to refer to how we came up with the plan for those two ariticles.

Self-Review

In this section, please self-review (answer all questions) on a suitable review checklist prior to requesting review from others. Select a review checklist based on what content is being merged in; see the Review Checklists section.

Reviewer Instructions

Reviewers, please copy and paste a suitable review checklist into your review and answer all questions.

Appendix

This section should be the same for all PRs. Do not edit this section when creating a PR.

Review Checklists

Checklists maintained by the eLev lab for research repositories include:

• Report checklist
• Publication archive checklist (select a checklist from the Approach that corresponds to the step this PR seeks to complete).
• Standard checklist (if none of the above apply).

Standard checklist

1. Are all files under 300 kB (if not, please carefully assess whether it is worth committing them)? **Yes or No**
2. Are all files named according to the appropriate [naming convention](https://github.com/Severson-Group/research-repo-template?tab=readme-ov-file#file-naming), i.e., dash-case, camelCase, snake case? **Yes or No**
3. Do all Markdown files follow the [CONTRIBUTING article template](https://github.com/Severson-Group/.github/blob/main/CONTRIBUTING.md#markdown-documentation-template)? **Yes or No**
4. Do all links work in the material that the PR is adding? **Yes or No**
5. Is the PR configured to close the correct issue(s)? **Yes or No**
6. Did the PR fully address the `Approach` section of the issue(s) it is closing? **Yes or No**

Please work on addressing any **No** items.

[noguchi-takahiro]

Hello @elsevers, the AMDC article of Autogen is ready. See the following rendered articles:

• Article: Control with AMDC Using Simulink Autogen.pdf
• Tutorial: Tutorial_ Autogen - AMDC Platform.pdf).

I think we can have better block diagram for the article, but we can discuss.

[noguchi-takahiro]

Hello @elsevers, I updated the file organization for autogen folder. See the following rendered articles:

• Article: Control with AMDC Using Simulink Autogen.pdf
• Tutorial: Tutorial_ Autogen - AMDC Platform.pdf.

[elsevers]

Thanks @noguchi-takahiro. I have it on my queue.

[elsevers]

Following up on out 5/11 meeting:

• Need to update simulink to follow new style guidelines
• Take a look at the top two discussions here: https://github.com/Severson-Group/AMDC-Examples/discussions . Do we need to update out article to factor any of this in?

[noguchi-takahiro]

Hello @elsevers, I have addressed the item 1 in this comment. See the following rendered articles:

• Article: Control with AMDC Using Simulink Autogen.pdf
• Tutorial: Tutorial_ Autogen - AMDC Platform.pdf

I also updated the index so that those contents show up on the left banner.

@Daehoon-Sung regarding the following comment, can you take a few minutes to review this discussion and make sure if we addressed all of these within the autogen article?

Take a look at the top two discussions here: https://github.com/Severson-Group/AMDC-Examples/discussions . Do we need to update out article to factor any of this in?

My takeaway is we already addressed these but I wanted to double check this with you.

[mhmokhtarabadi]

Thank you @Daehoon-Sung and @noguchi-takahiro for this nice article. I have some inline comments. Feel free to comment on what you think if you don't like my suggestions.

[mhmokhtarabadi]

@noguchi-takahiro, do you think we should follow PR https://github.com/Severson-Group/KnowledgeBase/pull/366 as the reference for naming the variables here?

[noguchi-takahiro]

Thank you @mhmokhtarabadi, can I request you to update naming convention for both setup.m and setup_model.slx and generate_duty.slx for me?

[noguchi-takahiro]

Thank you @mhmokhtarabadi. I addressed your feedback. Can you kindly update naming convention based on this latest article here or https://github.com/Severson-Group/KnowledgeBase/pull/366?

[AwesomeTornado]

Please make sure images are viewable in dark mode. See #177 and #173 for more info.

Graphics with white backgrounds that are already readable in dark mode don't need to be changed.

[noguchi-takahiro]

Thank you @AwesomeTornado. I checked the issue/PR you mentioned. I have a question:

Regarding the second item, I wonder how we can easily create the dark mode version of graphics? Do you use Inkscape or something coding?

[AwesomeTornado]

I wonder how we can easily create the dark mode version of graphics? Do you use Inkscape or something coding?

@noguchi-takahiro I use Inkscape. First, press CTRL + SHIFT + D to open document settings. The Page, Border, and Desk options control what the default background color is. By changing these to be very dark, you can simulate what dark mode users will see.

To fix graphics, click on elements that are difficult to see, then use the properties panel on the right to increase the lightness of the fill, the outline, or both.

Once the image is readable, click Save As and append -dark to the filename.