|
| 1 | +[INCLUDE=style/lncs] |
| 2 | +Title : TITLE OF YOUR PAPER, IN CAPITAL LETTERS CENTERED ON PAGE, USING ONE OR MORE LINES AS NECESSARY |
| 3 | +Subtitle : An optional subtitle. |
| 4 | + |
| 5 | +Author : First Author Name |
| 6 | +Affiliation : Research institute |
| 7 | + |
| 8 | + |
| 9 | +Author : My co-author 1 |
| 10 | +Affiliation : Other institute |
| 11 | + |
| 12 | + |
| 13 | +Author : My co-author 2 |
| 14 | +Affiliation : Other institute |
| 15 | + |
| 16 | + |
| 17 | +Bibliography : references.bib |
| 18 | +Logo : False |
| 19 | +Tex Header : |
| 20 | + \def\refname{&name-references;} |
| 21 | +name-references : REFERENCES |
| 22 | + |
| 23 | +[TITLE] |
| 24 | + |
| 25 | +~ Abstract |
| 26 | +Papers should follow standard technical paper format, an abstract |
| 27 | +followed by the more detailed presentation. The abstract should be typed |
| 28 | +on this area of the first page, with the presentation following after two |
| 29 | +lines of space. |
| 30 | +~ |
| 31 | + |
| 32 | +[editor]: https://www.madoko.net/editor.html "Madoko.net Editor" |
| 33 | +[reference-manual]: http://research.microsoft.com/en-us/um/people/daan/madoko/doc/reference.html "Madoko Reference Manual" |
| 34 | +[femtc2016]: https://github.com/thunderheadeng/femtc2016 |
| 35 | + |
| 36 | + |
| 37 | +# GENERAL INSTRUCTIONS { #sec-intro } |
| 38 | +You are encouraged to use the [Madoko.net Editor][editor] while using |
| 39 | +the [Madoko Reference Manual][reference-manual] to edit/commit your |
| 40 | +documents into the 'authoring' branch of the [femtc2016] GitHub repository. |
| 41 | +More information about this method of contribution will be covered below. |
| 42 | + |
| 43 | +Text styling, links, sub- and super-script, footnotes and other topics |
| 44 | +are covered in section [Syntax: Inline |
| 45 | +elements](http://research.microsoft.com/en-us/um/people/daan/madoko/doc/reference.html#sec-syntax--inline-elements) |
| 46 | +of the manual. |
| 47 | + |
| 48 | +Headings, Figures and Tables, Lists, Code Blocks, Mathematics, etc. are |
| 49 | +covered in section [Syntax: Block |
| 50 | +elements](http://research.microsoft.com/en-us/um/people/daan/madoko/doc/reference.html#sec-syntax--block-elements) |
| 51 | +of the manual. |
| 52 | + |
| 53 | +The target length for submitted and invited papers is about eight pages. |
| 54 | +This length includes all figures and tables. However, because the |
| 55 | +Proceedings will not be printed on paper, there is no maximum limit on |
| 56 | +the number of pages. You are free to exceed the target length of eight |
| 57 | +pages. |
| 58 | + |
| 59 | +Please watch this short YouTube Video for a tutorial on how to use the system as intended. |
| 60 | + |
| 61 | +# MAIN HEADINGS LIKE THIS STYLE |
| 62 | +Main Headings are all upper case letters and underlined. In Madoko, a |
| 63 | +Single '#' symbol at the start of the line, followed by a space and then |
| 64 | +the heading text. |
| 65 | + |
| 66 | +## Subheadings Like This Style |
| 67 | +Subheadings within sections follow the same format as section titles, but |
| 68 | +with upper and lower case. In Madoko, a Double '#' symbol at the start of |
| 69 | +the line, followed by a space and then the heading text. |
| 70 | + |
| 71 | +### Subsubheadings like this style |
| 72 | +Subsubheadings have no underline, and only the first letter capitalized. |
| 73 | +In Madoko, a Triple '#' symbol at the start of the line, followed by a |
| 74 | +space and then the heading text. |
| 75 | + |
| 76 | +# FIGURES, TABLES, AND EQUATIONS |
| 77 | +Original drawings and photos may be included in your paper as figures. |
| 78 | +Diagrams may be in color. |
| 79 | + |
| 80 | +Figures and tables should immediately follow first mention of them in the |
| 81 | +text and can be placed in one column, or in the case of wider figures, |
| 82 | +can cover two columns (but only at the top or bottom of the page). The |
| 83 | +caption should start with either the word “figure” spelled out or |
| 84 | +abbreviated, followed by the figure number (i.e., Figure 1 or Fig. 1). |
| 85 | +The figure caption should be followed by a single line of space before |
| 86 | +the text resumes. |
| 87 | + |
| 88 | +## Figures |
| 89 | +Figure [#fig-smokeview] in Section [#sec-intro] shows an image from an |
| 90 | +older version of Smokeview. Note that you can drag&drop images into the |
| 91 | +editor pane to include them in the document, and similarly with bibtex |
| 92 | +files, latex style files, etc. |
| 93 | + |
| 94 | +~ Figure { #fig-smokeview; caption:"Illustration of placement of figure and caption. (use the `.wide` class for wide figure)."} |
| 95 | +![Ex1_0] |
| 96 | +~ |
| 97 | +[Ex1_0]: images/Ex1_0.png "Ex1_0" { width:auto; max-width:90% } |
| 98 | + |
| 99 | +~ Note |
| 100 | +Images larger than about 1Mb in size will be rejected by the Madoko.net server. |
| 101 | +~ |
| 102 | + |
| 103 | +## Tables |
| 104 | +Table [#table-sample] shows an example full width table figure. |
| 105 | + |
| 106 | +~ TableFigure { #table-sample; caption: "Modelle mit unterschiedlich geschätztem baseline hazard"; .wide } |
| 107 | +| | $c(t)$ |||| |
| 108 | +| |---------|---------|---------|-----------| |
| 109 | +| | (A0) | (A1) | (A2) | (A3) | |
| 110 | +| | ohne | Log | Polynom | Stückweise| |
| 111 | +| | | | | konstant | |
| 112 | +|:---------------|:-------:|:-------:|:-------:|:---------:| |
| 113 | +| Log likelihood | -6.798 | -6.733 | -6.715 | -6.686 | |
| 114 | +| Pseudeo $R^{2}$| 0,048 | 0,057 | 0,059 | - | |
| 115 | +| AIC | 13.615 | 13.489 | 13.456 | 13.483 | |
| 116 | +| BIC | 13.711 | 13.594 | 13.580 | 14.009 | |
| 117 | +| N | 105.484 | 105.484 | 105.484 | 105.484 | |
| 118 | +|----------------|---------|---------|---------|-----------| |
| 119 | +~ |
| 120 | + |
| 121 | +## Equations |
| 122 | +Standard terminology should be used in equations. If possible, keep |
| 123 | +equations to one column. All equations should be numbered. A definition |
| 124 | +of $e$ is shown in Equation [#euler]: |
| 125 | + |
| 126 | +~ Equation { #euler } |
| 127 | +e = \lim_{n\to\infty} \left( 1 + \frac{1}{n} \right)^n |
| 128 | +~ |
| 129 | + |
| 130 | +Or to use &logolatex; to align equations. |
| 131 | + |
| 132 | +~ Equation { #eq-alignment; caption:"Alignment example" } |
| 133 | +\begin{aligned} |
| 134 | + f(x) &= a x^2+b x +c & g(x) &= d x^3 \\ |
| 135 | + f'(x) &= 2 a x +b & g'(x) &= 3 d x^2 |
| 136 | +\end{aligned} |
| 137 | +~ |
| 138 | + |
| 139 | +# FUN CONTENT EXAMPLES |
| 140 | +Let's program some JavaScript: |
| 141 | +``` javascript |
| 142 | +function hello() { |
| 143 | + return "hello world!" |
| 144 | +} |
| 145 | +``` |
| 146 | +Here is a footnote[^fn] reference. |
| 147 | +[^fn]: This is the content of the example footnote. |
| 148 | + You can continue a footnote by indenting content. |
| 149 | + And notice the back link. |
| 150 | + |
| 151 | +# BIBLIOGRAPHY AND REFERENCES |
| 152 | +When references are used in the text, tie them to an alphabetical (by |
| 153 | +principal author) list of references to be included as the last item of |
| 154 | +your paper. The format commonly used in scientific literature follows: |
| 155 | + |
| 156 | +Smith, J. S., Bloggs, R. T. and Jones, E. R. (1974), "Magnetic Anomalies |
| 157 | +in Geothermal Systems", Journal of Fluid Mechanics, 254, 73-79 |
| 158 | + |
| 159 | +Leslie Lamport, LaTeX: A Document Preparation System (2nd Edition), Addison-Wesley, 1994 |
| 160 | + |
| 161 | +When using Madoko, edit the content of the .bib file in the document |
| 162 | +folder, and use the reference methods as shown in the [Bibliography and |
| 163 | +Citations |
| 164 | +Section](http://research.microsoft.com/en-us/um/people/daan/madoko/doc/reference.html#sec-bib) |
| 165 | +of the Madoko Manual. |
| 166 | + |
| 167 | +A bibliography file consists of all your references in the BibTeX format, for example: |
| 168 | + |
| 169 | + @BOOK{ Knuth:TeX, |
| 170 | + author = "Knuth, Donald E.", |
| 171 | + title = "The {\TeX} book", |
| 172 | + publisher= "Addison-Wesley", |
| 173 | + year = 1984 |
| 174 | + } |
| 175 | + |
| 176 | +Entries in the bibliography files can now be referenced using semi-colon |
| 177 | +separated references, for example: |
| 178 | +``` Markdown |
| 179 | +Read about LaTeX and TeX [@Knuth:TeX; @Lamport:LaTeX]. |
| 180 | +``` |
| 181 | +Results in: Read about LaTeX and TeX [@Knuth:TeX; @Lamport:LaTeX]. |
| 182 | + |
| 183 | +Please include full title of journal articles or other references, |
| 184 | +journal, volume, date, pages. There is a nice [table on |
| 185 | +Wikipedia](https://en.wikibooks.org/wiki/LaTeX/Bibliography_Management#BibTeX) |
| 186 | +that shows all of the different data fields for the BibTeX file. |
| 187 | + |
| 188 | +# PAPER DEADLINE |
| 189 | +Your paper, in final form, must be received by October 15th, 2016. The |
| 190 | +best way to edit and submit is to use the Madoko [editor] to edit your |
| 191 | +document in the 'authoring' branch of the GitHub [femtc2016] repository. |
| 192 | +If you choose to use some other document format and editing tool, PDF |
| 193 | +format is preferred, but ODT, DOC, or DOCX formats are acceptable. Please |
| 194 | +e-mail the files to [ [email protected]][emaillink]. |
| 195 | + |
| 196 | +# PRESENTATION |
| 197 | +Each author must present his/her paper within the allotted time, allowing |
| 198 | +for some minutes of open discussion. The session chair is responsible for |
| 199 | +keeping authors within their time limit, in order to ensure that each |
| 200 | +author has enough time for their presentation. When preparing your |
| 201 | +presentation slides, make sure they are clear and large enough so that |
| 202 | +your audience can read them from as far as 80 feet away. |
| 203 | + |
| 204 | +All presentations will be made using the computer projector available in |
| 205 | +the conference room. We will not have overhead projectors or slide |
| 206 | +projectors in the meeting rooms. |
| 207 | + |
| 208 | +Your presentation, in final form, must be received by **October 15th, |
| 209 | +2016**. A final commit of the files to the GitHub repository is |
| 210 | +preferred. Once the final draft is complete and reviewed it will be |
| 211 | +merged into the master branch of the repository. If you decide to use |
| 212 | +some other tool for creating your presentation, PDF format is preferred, |
| 213 | +but ODP, PPT, or PPTX formats are acceptable. Please e-mail the files |
| 214 | +to [ [email protected]][emaillink]. |
| 215 | + |
| 216 | +All presentations will be pre-loaded on the computers that are present. |
| 217 | +Please note that this approach will make it necessary for us to receive |
| 218 | +the presentation files prior to the conference. If you have a different |
| 219 | +software requirement, it should still be possible for you to attach your |
| 220 | +own computer to the projector if you bring it with you. This is not |
| 221 | +optimal, as it takes time and slows down the session. |
| 222 | + |
| 223 | +# CONFERENCE CONTENT DISTRIBUTION |
| 224 | +The papers and presentation materials will be made available online |
| 225 | +during and after the conference. In addition, the organizers are planning |
| 226 | +to may broadcast live presentations online during the event. The papers, |
| 227 | +presentations, and videos will be archived and made available on the web |
| 228 | +after the conference. |
| 229 | + |
| 230 | +Author(s) retain all rights to submitted material. The organizers are |
| 231 | +granted a non-exclusive right to copy and redistribute conference |
| 232 | +material submitted by the author(s). |
| 233 | + |
| 234 | +[BIB] |
| 235 | + |
| 236 | +&pagebreak; |
| 237 | + |
| 238 | +# An appendix { @h1:"A" } |
| 239 | +"All the same, I should like it all plain and clear," said he |
| 240 | +obstinately, putting on his business manner (usually reserved for people |
| 241 | +who tried to borrow money off him), and doing his best to appear wise and |
| 242 | +prudent and professional and live up to Gandalf's recommendation. "Also I |
| 243 | +should like to know about risks, out-of-pocket expenses, time required |
| 244 | +and remuneration, and so forth" -- by which he meant: "What am I going to |
| 245 | +get out of it? and am I going to come back alive?" |
| 246 | + |
| 247 | +# Conclusion |
| 248 | +If you have any questions concerning your paper and/or the Conference, |
| 249 | +please email us at [ [email protected]][emaillink]. |
0 commit comments