main.typ

//==============================================================================
// main.typ 2023-11-17 Alexander Von Moll
// Template for IFAC meeting papers
//
// Adapted from ifacconf.tex by Juan a. de la Puente
//==============================================================================

#import "@preview/abiding-ifacconf:0.1.0": *
#show: ifacconf-rules
#show: ifacconf.with(
  title: "Style for IFAC Conferences & Symposia: Use Title Case for Paper Title",
  authors: (
    (
      name: "First A. Author",
      email: "author@boulder.nist.gov",
      affiliation: 1,
    ),
    (
      name: "Second B. Author, Jr.",
      email: "author@lamar.colostate.edu",
      affiliation: 2,
    ),
    (
      name: "Third C. Author",
      email: "author@snu.ac.kr",
      affiliation: 3,
    ),
  ),
  affiliations: (
    (
      organization: "National Institute of Standards and Technology",
      address: "Boulder, CO 80305 USA",
    ),
    (
      organization: "Colorado State University",
      address: "Fort Collins, CO 80523 USA",
    ),
    (
      department: "Electrical Engineering Department",
      organization: "Seoul National University",
      address: "Seoul, Korea",
    ),
  ),
  abstract: [
    These instructions give you guidelines for preparing papers for IFAC technical meetings. Please use this document as a template to prepare your manuscript. For submission guidelines, follow instructions on paper submission system as well as the event website.
  ],
  keywords: ("Five to ten keywords", "preferably chosen from the IFAC keyword list."),
  sponsor: [
    Sponsor and financial support acknowledgment goes here. Paper titles should be written in uppercase and lowercase letters, not all uppercase.
  ],
)

= Introduction

This document is a template for Typst.
Running the command `typst init @preview/abiding-ifacconf` will generate the files needed to get started..
The template files are also available on github at #link("https://github.com/avonmoll/ifac-typst")[`https://github.com/avonmoll/ifacconf-typst`].

Please stick to the format defined by the `ifacconf` function, and do not change the margins or the general layout of the paper.
It is especially important that you do not put any running header/footer or page number in the submitted paper.#footnote[This is the default for the provided class file.]
Use _italics_ for emphasis; do not underline.

Page limits may vary from conference to conference.
Please observe the page limits of the event for which your paper is intended.

= Procedure for Paper Submission

Next we see a few subsections.

== Review Stage

For submission guidelines, follow instructions on paper submission system as well as the event website.

Note that conferences impose strict page limits, so it will be better for you to prepare your initial submission in the camera ready layout so that you will have a good estimate for the paper length.
Additionally, the effort required for final submission will be minimal.

== Equations

Some words might be appropriate describing equation @sample, if 
we had but time and space enough. 

$
(diff F) / (diff t) = D (diff^2 F) / (diff x^2)
$ <sample>

See @Abl56 @AbTaRu54 @Keo58, and @Pow85.

=== Example. 
This equation goes far beyond the celebrated theorem ascribed to the great Pythagoras by his followers.

#theorem[
The square of the length of the hypotenuse of a right triangle equals the sum of the squares of the lengths of the other two sides.
]
#proof[
The square of the length of the hypotenuse of a right triangle equals the sum of the squares 
of the lengths of the other two sides.
]

// There are a number of predefined theorem-like environments in
// template.typ:
// 
// #theorem[ ... ]        // Theorem
// #lemma[ ... ]          // Lemma
// #claim[ ... ]          // Claim
// #conjecture[ ... ]     // Conjecture
// #corollary[ ... ]      // Corollary
// #fact[ ... ]           // Fact
// #hypothesis[ ... ]     // Hypothesis
// #proposition[ ... ]    // Proposition
// #criterion[ ... ]      // Criterion

== Figures

To insert figures, use the `#figure` function.
See @bifurcation for an example which was generated by the following code.

```
#figure(
  image("bifurcation.jpg", width: 8.4cm)
  caption: [Bifurcation: ...]
) <bifurcation>
```

#figure( 
  // image("bifurcation.jpg", width: 8.4cm),
  rect(width: 8.4cm, height: 6.3cm),  // bifurcation.jpg excluded intentionally to save space
  caption: [Bifurcation: Plot of local maxima of $x$ with damping $a$ decreasing],
  placement: auto
) <bifurcation>

Figures must be centered, and have a caption at the bottom. 

== Tables

Tables must be centered and have a caption above them, numbered with Arabic numerals.
See @margins for an example.

#tablefig(
  table(
    columns: 4,
    align: center + horizon,
    stroke: none,
    inset: 3pt,
    [Page], [Top], [Bottom], [Left/Right],
    table.hline(),
    [First], [3.5], [2.5], [1.5],
    [Rest], [2.5], [2.5], [1.5],
    table.hline(),
  ),
  caption: [Margin settings],
) <margins>

== Final Stage

Authors are expected to mind the margins diligently.
Papers need to be stamped with event data and paginated for inclusion in the proceedings.
If your manuscript bleeds into margins, you will be required to resubmit and delay the proceedings preparation in the process.

=== Page margins.
See @margins for the page margins specification.
All dimensions are in _centimeters_.

== PDF Creation

All fonts must be embedded/subsetted in the PDF file.
This is handled by Typst.

== Copyright Form

IFAC will put in place an electronic copyright transfer system in due course.
Please _do not_ send copyright forms by mail or fax.
More information on this will be made available on IFAC website.

= Units

Use SI as primary units.
Other units may be used as secondary units (in parentheses).
This applies to papers in data storage.
For example, write "$15" Gb/cm"^2$ ($100" Gb/in"^2$)". 
An exception is when English units are used as identifiers in trade, such as "3.5 in disk drive".
Avoid combining SI and other units, such as current in amperes and magnetic field in oersteds.
This often leads to confusion because equations do not balance dimensionally.
If you must use mixed units, clearly state the units for each quantity in an equation.
The SI unit for magnetic field strength $bold(upright(H))$ is $"A/m"$.
However, if you wish to use units of T, either refer to magnetic flux density $bold(upright(B))$ or magnetic field strength symbolized as $mu_0 bold(upright(H))$.
Use the center dot to separate compound units, e.g., "$upright(A) dot.c upright(m)^2$".

= Helpful Hints

== Figures and Tables

Figure axis labels are often a source of confusion.
Use words rather than symbols.
As an example, write the quantity "Magnetization", or "Magnetization M", not just "M".
Put units in parentheses.
Do not label axes only with units.
For example, write "Magnetization ($upright(A)$/$upright(m)$)" or "Magnetization ($upright(A)upright(m)^(-1)$)", not just "$upright(A)$/$upright(m)$".
Do not label axes with a ratio of quantities and units.
For example, write "Temperature ($upright(K)$)", not "$"Temperature"$/$upright(K)$".

Multipliers can be especially confusing.
Write "Magnetization ($"kA"/upright(m)$)" or "Magnetization ($10^3 upright(A)$/$upright(m)$)''.
Do not write "Magnetization $(upright(A)$/$upright(m)) times 1000$" because the reader would not know whether the axis label means $16000 med upright(A)$/$upright(m)$ or $0.016 med upright(A)$/$upright(m)$.

== References

Use Harvard style references (see at the end of this document).
With Typst, you can process an external bibliography database in the BibTeX format (`.bib`) or Hayagriva (a Rust-based bibliography management system based on YAML) formats.
Footnotes should be avoided as far as possible.
Please note that the references at the end of this document are in the preferred referencing style.
Papers that have not been published should be cited as "unpublished".
Capitalize only the first word in a paper title, except for proper nouns and element symbols.

== Abbreviations and Acronyms

Define abbreviations and acronyms the first time they are used in the text, even after they have already been defined in the abstract.
Abbreviations such as IFAC, SI, ac, and dc do not have to be defined.
Abbreviations that incorporate periods should not have spaces: write "C.N.R.S.", not "C. N. R. S."
Do not use abbreviations in the title unless they are unavoidable (for example, "IFAC" in the title of this article).

== Equations

Number equations consecutively with equation numbers in parentheses flush with the right margin, as in @sample.
To make your equations more compact, you may use the solidus (/), the $exp$ function, or appropriate exponents.
Use parentheses to avoid ambiguities in denominators.
Punctuate equations when they are part of a sentence, as in

$
integral_0^(r_2) & F(r, phi.alt) upright(d)r upright(d) phi.alt = [sigma r_2 \/ (2 mu_0)] \
  & dot.c integral_0^"inf" exp(- lambda |z_j - z_i|) lambda^(-1) J_1 (lambda r_2) J_0 (lambda r_i) upright(d) lambda
$ <sample2>

Be sure that the symbols in your equation have been defined before the equation appears or immediately following.
Italicize symbols ($T$ might refer to temperature, but T is the unit tesla).
Refer to "@sample", not "Eq. @sample" or "equation @sample", except at the beginning of a sentence: "Equation @sample is ...".

== Other Recommendations

Use one space after periods and colons.
Hyphenate complex modifiers: "zero-field-cooled magnetization".
Avoid dangling participles, such as, "Using (1), the potential was calculated" (it is not clear who or what used (1)).
Write instead: "The potential was calculated by using (1)", or "Using (1), we calculated the potential".

A parenthetical statement at the end of a sentence is punctuated outside of the closing parenthesis (like this).
(A parenthetical sentence is punctuated within the parentheses.)
Avoid contractions; for example, write "do not" instead of "don't".
The serial comma is preferred: "A, B, and C" instead of "A, B and C".

= Conclusion

A conclusion section is not required.
Although a conclusion may review the main points of the paper, do not replicate the abstract as the conclusion.
A conclusion might elaborate on the importance of the work or suggest applications and extensions.

= Acknowledgments

Place acknowledgments here.

// Display bibliography.
#bibliography("refs.bib")

#appendix[Summary of Latin Grammar]

#appendix[Some Latin Vocabulary]