-
Notifications
You must be signed in to change notification settings - Fork 0
/
Copy pathmain.tex
executable file
·1289 lines (1019 loc) · 44.7 KB
/
main.tex
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387
388
389
390
391
392
393
394
395
396
397
398
399
400
401
402
403
404
405
406
407
408
409
410
411
412
413
414
415
416
417
418
419
420
421
422
423
424
425
426
427
428
429
430
431
432
433
434
435
436
437
438
439
440
441
442
443
444
445
446
447
448
449
450
451
452
453
454
455
456
457
458
459
460
461
462
463
464
465
466
467
468
469
470
471
472
473
474
475
476
477
478
479
480
481
482
483
484
485
486
487
488
489
490
491
492
493
494
495
496
497
498
499
500
501
502
503
504
505
506
507
508
509
510
511
512
513
514
515
516
517
518
519
520
521
522
523
524
525
526
527
528
529
530
531
532
533
534
535
536
537
538
539
540
541
542
543
544
545
546
547
548
549
550
551
552
553
554
555
556
557
558
559
560
561
562
563
564
565
566
567
568
569
570
571
572
573
574
575
576
577
578
579
580
581
582
583
584
585
586
587
588
589
590
591
592
593
594
595
596
597
598
599
600
601
602
603
604
605
606
607
608
609
610
611
612
613
614
615
616
617
618
619
620
621
622
623
624
625
626
627
628
629
630
631
632
633
634
635
636
637
638
639
640
641
642
643
644
645
646
647
648
649
650
651
652
653
654
655
656
657
658
659
660
661
662
663
664
665
666
667
668
669
670
671
672
673
674
675
676
677
678
679
680
681
682
683
684
685
686
687
688
689
690
691
692
693
694
695
696
697
698
699
700
701
702
703
704
705
706
707
708
709
710
711
712
713
714
715
716
717
718
719
720
721
722
723
724
725
726
727
728
729
730
731
732
733
734
735
736
737
738
739
740
741
742
743
744
745
746
747
748
749
750
751
752
753
754
755
756
757
758
759
760
761
762
763
764
765
766
767
768
769
770
771
772
773
774
775
776
777
778
779
780
781
782
783
784
785
786
787
788
789
790
791
792
793
794
795
796
797
798
799
800
801
802
803
804
805
806
807
808
809
810
811
812
813
814
815
816
817
818
819
820
821
822
823
824
825
826
827
828
829
830
831
832
833
834
835
836
837
838
839
840
841
842
843
844
845
846
847
848
849
850
851
852
853
854
855
856
857
858
859
860
861
862
863
864
865
866
867
868
869
870
871
872
873
874
875
876
877
878
879
880
881
882
883
884
885
886
887
888
889
890
891
892
893
894
895
896
897
898
899
900
901
902
903
904
905
906
907
908
909
910
911
912
913
914
915
916
917
918
919
920
921
922
923
924
925
926
927
928
929
930
931
932
933
934
935
936
937
938
939
940
941
942
943
944
945
946
947
948
949
950
951
952
953
954
955
956
957
958
959
960
961
962
963
964
965
966
967
968
969
970
971
972
973
974
975
976
977
978
979
980
981
982
983
984
985
986
987
988
989
990
991
992
993
994
995
996
997
998
999
1000
%\documentclass[english]{ipsj}
%\documentclass[english,preprint]{ipsj}
\documentclass[english,preprint,JIP]{ipsj}
\usepackage{graphicx}
\usepackage{latexsym}
\def\Underline{\setbox0\hbox\bgroup\let\\\endUnderline}
\def\endUnderline{\vphantom{y}\egroup\smash{\underline{\box0}}\\}
\def\|{\verb|}
\setcounter{volume}{26}% vol25=2017
\setcounter{number}{1}%
\setcounter{page}{1}
\received{2016}{3}{4}
%\rereceived{2011}{10}{1} % optional
%\rerereceived{2011}{10}{31} % optional
\accepted{2016}{8}{1}
\usepackage[varg]{txfonts}%%!!
\makeatletter%
\input{ot1txtt.fd}
\makeatother%
\begin{document}
\title{Compilation for a Version Polymorphic\\Object-Oriented Programming Language}
\affiliate{TIT}{Tokyo Institute of Technology,
Meguro, Tokyo 152--8550, Japan}
\author{Luthfan Anshar Lubis}{TIT}[luthfanlubis@prg.is.titech.ac.jp]
\author{Yudai Tanabe}{TIT}
\author{Masuhara Hidehiko}{TIT}
\begin{abstract}
% Programming with versions (PWV) introduced the notion of versions into the language semantics
% and allowed version-safe multi-version programming. BatakJava, an object-oriented
% implementation of this concept, takes a non-restrictive approach to PWV that allows
% different versions of a class to interact together. To ensure version safety,
% BatakJava requires every type in a program to be fixed to a particular version after
% compilation. However, the nature of multi-version programming inevitably
% require some types in a definition to be used with different combination of versions.
% To solve this problem, we propose the use of parameterized versions to allow version
% polymorphic definitions. This paper presents the design for a version polymorphic
% extension of BatakJava,
% an implementation that modifies BatakJava's type analysis and code generation,
% and a case study to demonstrate the better flexibility of programming with version
% polymorphism.
Programming with versions (PWV) introduces the notions of versions into the
language semantics and allows for version-safe multi-version programming.
BatakJava is an object-oriented implementation of PWV that adds versions
as an attribute of a class, where different versions of a class can coexist and
interact with each other in the same program.
To ensure version safety, BatakJava uses a constraint-based type system during
compilation that
solves for a fixed version assignment for every type instance in the program.
However, this compilation scheme significantly reduces the flexibility of
multi-version programming that may require type instances to be used with
different version assignments.
To solve this problem, we propose the use of parameterized versions to allow
version polymorphic definitions.
This paper presents the design for a version polymorphic extension of BatakJava,
its implementation that modifies the original type analysis and code generation,
and a case study to demostrate the improved flexibility of multi-version
programming with version polymorphism.
\end{abstract}
\begin{keyword}
object-orientation, versioning, software evolution
\end{keyword}
\maketitle
%1
\section{Introduction}
The Information Processing Society of Japan (IPSJ) publishes Journal of
Information Processing (JIP) as its flagship international journal.
Thus far, the JIP adopted the landscape A4 format for publishing papers,
but it has changed this format to the portrait A4 format because of many
requests from authors. Corresponding to this format change, the JIP
accepts the portrait A4 format for submitting papers.
Following with this change, we, the Editorial Board of the JIP, prepared
a new style file for \LaTeX\@. In this manuscript, we first describe
the usage of the style file. The basic strategy of the new style file
is to require no special knowledge of command usage that does not use
standard \LaTeX commands. Authors of a paper can use standard \LaTeX
commands to keep within the formatting restrictions of the paper, such
as setting space pitches and margins. The guideline of the paper format
will be described in Section~\ref{body}. Since this manuscript itself
also is written with the style file, we hope it will help with writing a
paper.
The Editorial Board of the JIP has also prepared a ``Dos and Don'ts''
list of matters an author should consider while writing a paper. We
have added the list to the latter portion of this manuscript. Please
use the list as a checklist for preparing to submit a paper.
%2
\section{Flow from Submission to Publishing}
%2.1
\subsection{Preparation}
The JIP author's kit including the \LaTeX style files can be downloaded
from the following URL:
\begin{quote}
\small
\|http://www.ipsj.or.jp/journal/submit/style.html|
\end{quote}
The kit includes the following files:
\begin{enumerate}
\item \|ipsj.cls|: style file for ipsj journals
\item \|ipsjpref.sty|: style for the foreword
\item \|jsample.tex|: source for the Japanese version of this guide
\item \|esample.tex|: source of this guide
\item \|ipsjsort-e.bst|: bibtex style (sorted)
\item \|ipsjunsrt-e.bst|: bibtex style (unsorted)
\item \|bibsample.bib|: sample of bibliographic data (Japanese)
\item \|ebibsample.bib|: sample of bibliographic data (English)
\item \|ipsjtech.sty|: style file for technical report
\item \ \|tech-jsample.tex|: source for the Japanese version of technical report
\item \ \|tech-esample.tex|: source for the English version of technical report
\end{enumerate}
Since {\LaTeXe} is required as an execution environment, please install
it.
Regarding manuscripts written with Microsoft Word, a corresponding
company will convert them into \LaTeX\@. This means that the Microsoft
Word format is used just a reference.
\footnotetext{The real author is the Editorial Board of JIP.}
%2.2
\subsection{Draft Submission}
First, generate a PDF file from your \LaTeX source and style file under
your {\LaTeXe} environment and check that the generated PDF file can be
read with the Adobe PDF reader. After that, register your email address
into the Paper Review Management System (PRMS) through the following
URL:
\begin{quote}
\small
\|https://mc.manuscriptcentral.com/ipsj|
\end{quote}
\noindent
The system will return an email including another URL for submitting
your paper. The manual for submission via the PRMS is available at the
following URL:
\begin{quote}
\small
\|http://www.ipsj.or.jp/english/jip/submit/manual/|
\|e_manual.html|
\end{quote}
The JIP adopts \textit{single blind review},
where you will not know reviewers' names.
%2.3
\subsection{Final Version}
After you receive the notification of acceptance, revise your paper in
accordance with the comments from the referees.
The layout of
figures and tables should be fixed. After that, \textit{check your paper
again and again to completely remove description errors}.
Send \textit{both the {\LaTeX} file package and the hard copy} to the
IPSJ\@. The standard contents of the file package are .tex and .bbl. If
you include PostScript files and/or special style files, add them into
the package. Note that \textit{you must not split your source into
multiple .tex files} because it is hard for printers to access multiple
files when they modify your source. Also, carefully make sure that the
package contains all necessary files, especially special style files.
Details on the file transfer, including its destination and packaging
method, will be provided to you by the IPSJ secretariat.
%2.4
\subsection{Proofreading, Typesetting, and Publishing}
The IPSJ may change terms in your paper as per its standard, and the
printing house may modify your source to make it fit the standard
printing style. Even if they make no changes, the result printed at the
printing house may be different from what you printed because of
differences in the {\LaTeX} execution environment. Therefore, the
galley proofs of your paper will be sent to you so that you can check if
those modifications and/or differences are acceptable. If not, correct
errors with red ink. Note that \textit{this proofreading is not for
correcting your errors}, which should have been corrected before sending
the final version.
Your paper will be typeset after errors you notify us about (if any) are
corrected and will be published as part of the JIP.
%3
\section{Guide for Formatting a Paper}
The JIP, as opposed to conference proceedings, has a traditional and
\textit{stiff} style. This makes the style files also \textit{stiff}
and strongly restricts customizability, which is one of the most useful
features of {\LaTeX}. For example, you must not change \textit{style
parameters}, such as \verb+\texheight+. It is not easy to show which
customizations are allowed, but the rule ``Don't tamper with it unless
you are confident'' should suffice.
Note that if you do something you should not, \textit{you may not have
error messages but simply unattractive results}.
The source file must use the following format. Underlined parts can be
omitted from draft versions.
%4
\section{Configuration of Paper}
\label{body}
The source file must use the following format. Underlined parts can be
omitted from draft versions. Note that a few additional commands, shown
in A.1 of the Appendix, are available for a paper included in the
Transactions.
\vskip\baselineskip
\noindent
\|\documentclass[JIP]{ipsj}|\\
\quad Specify other option styles if necessary.\\
\quad Specify auxiliary styles with \|\usepackage|.\\
\\
\Underline{\|\setcounter{|{\bf volume}\|}{<volume>}|}\\
\Underline{\|\setcounter{|{\bf number}\|}{<number>}|}\\
\Underline{\|\setcounter{|{\bf page}\|}{<first-page>}|}\\
\Underline{\|\|{\bf received}\|{<year>}{<month>}{<day>}|}\\
\Underline{\|\|{\bf accepted}\|{<year>}{<month>}{<day>}|}\\
\quad Define your own macros if necessary.\\\\
\quad If you cannot use the \|txfonts| package, please do not use the following command\\
\Underline{\|\usepackage[varg]{txfonts}|}\\
\Underline{\|\makeatletter|}\\
\Underline{\|\input{ot1txtt.fd}|}\\
\Underline{\|\makeatother|}\\\\
\|\begin{document}|\\[.5em]
\|\title{<title>}|\\[.5em]
\Underline{\|\affiliate{<affiliation-label>}{<affiliation>}|}\\\\
\quad Declare current affiliation with \|\paffilabel| if necessary.\\
\Underline{\|\paffiliate{<affiliation-label>}{<affiliation>}|}\\\\
\Underline{\|\author{1st-author}{affiliation-label}[E-mail]|}\\
\Underline{\|\author{2nd-author}{affiliation-label}|}\\\\
\|\begin{abstract}|\\
\quad\|<abstract>|\\
\|\end{abstract}|\\\\
\|\begin{keyword}|\\
\quad\|<keyword>|\\
\|\end{keyword}|\\\\
\|\maketitle|\\\\
\|\section{|heading-of-1st-section\|}|\\
\dots\dots\dots\dots\dots\\
\quad \|<main text>|\\
\dots\dots\dots\dots\dots\\\\
\quad Put acknowledgments here with the acknowledgment environment if any.\\
\|\begin{acknowledgment}|\\
\|\end{acknowledgment}|\\\\
\|\begin{thebibliography}{99}%9 or 99|\\
\|\bibitem{1}|\\
\|\bibitem{2}|\\
\|\end{thebibliography}|\\\\
\quad Put appendices here following \|\appendix| if any.\\
\|\appendix|\\
\|\section{|heading-of-1st-section\|}|\\\\
\Underline{\|\begin{biography}|}\\
\Underline{\|\profile{<1st-author>}{<biography-of-1st-author>}|}\\
\Underline{\|\profile{<2nd-author>}{<biography-of-2nd-author>}|}\\
\Underline{\|\end{biography}|}\\
\|\end{document}|
%4.1
\subsection{Option Style}
The following six styles are available as optional arguments of the
\|\documentclass|. If the JIP option is not used, the program will use
the standard Japanese paper style as the default.
\begin{enumerate}
\item\|JIP|\footnote{English should be used for the English version of the Transactions.}
\quad For English documents
\item\|invited| \quad For invited papers
\item\|sigrecommended| \quad For recommended papers
\item\|technote| \quad For technical notes
\item\|preface| \quad For the preface of an issue
\end{enumerate}
Any combination of these options can be used.
If you specify auxiliary style files with the
\|\usepackage|, you must include them in the file package when you send
your final version to the IPSJ\@.
However, style files included in the {\LaTeXe} standard distribution
(e.g., graphicx) may be omitted. Note that style files may be
incompatible with the style of the Journal Transaction.
%4.1.1
\subsubsection{Optional style exclusively for technical reports}
In addition to the options described above,
an option intended exclusively for technical reports is available.
\begin{quote}
\|techrep|\quad technical report
\end{quote}
If \|\documentclass[techrep,JIP]{ipsj}| is used,
the technical-report style will be applied.
%4.2
\subsection{Title, Author Names, etc.}
Describe the title of your paper, author names and affiliations, and
abstract using the commands and environment shown in Section~\ref{body}.
Then, perform \verb+\maketitle+ to automatically put them at the
appropriate position. In the draft version, the title and abstract are
automatically printed onto separate pages, while author names and
affiliations are not printed in order to make your paper anonymous.
%4.2.1
\subsubsection{Title}
The title specified with \verb+\title+ is made centered. Even if the
title is too long to fit onto one line, \textit{an automatic line break
is not performed}. If your title is long, insert \verb+\\+ into the
appropriate positions to break the lines. A multiple line title is
first flushed left and then centered with respect to the widest line.
The title also appears in the header of odd numbered pages. If your
title is too long, provide a shortened title for the header to
\verb+\title+ as its optional argument as follows.
%4.2.2
\subsubsection{Author Name and Affiliation}
When indicating the affiliation of each author with a label (first
citation) and starting from the first author, by using \|\affiliate|,
numbered footnotes will be generated that show the affiliations. When
several authors are affiliated with the same organization, the
affiliation needs to be indicated only once. For the author's current
affiliation, use \|\paffiliate| and provide the label and affiliated
organization as before. If the affiliated organization arguments are
entered as current and a line break is inserted using \|\\|, the author
name will be automatically defined by \|\author|. Immediately after the
author's name, enter the affiliation label and the author's e-mail
address.
Where there are several authors, repeating \|\author| will generate
additional authors in sequence (two authors, three authors, and so
forth).
To add current affiliations or multiple affiliations, delineate the
affiliate label using commas to include additional data.
%4.2.3
\subsubsection{Abstract}
The abstract of your paper should only be used in the \verb+abstract+
environment.
%4.2.4
\subsubsection{Keywords}
The keywords of your paper should be included as the content for the
\verb+keyword+ environment.
%4.3
\subsection{Main part}
%4.3.1
\subsubsection{Sectioning}
{\LaTeX} standard commands such as \|\section| and \|\sub-| \|section|
are available for sectioning. The section heading of \|\section|
occupies two lines, while others are put into one line.
%4.3.2
\subsubsection{Fixed Baselines}
Each page of the JIP is formatted with the double-column style. The
printing tradition of double-column requires that a line in the left
column and its neighbor in the right column have the same baseline. To
meet this requirement, the style files carefully control the progression
of baselines when a vertical space is inserted for section titles and so
on.
%4.3.3
\subsubsection{Font Size}
You will see that various size fonts are used in the printed result of
your paper. Since these fonts are automatically and carefully chosen by
the style files, you are free from the headache of selecting proper
fonts. In fact, it is strongly recommended not to use
font-size-changing commands such as \verb+\large+ and \verb+\small+ in
the main text because they are quite harmful to retaining fixed
baselines.
%4.3.4
\subsubsection{Itemizing}
There is no special format for itemization. You can use the standard
\|enumerate|, \|itemize|, \|description| environment.
%4.3.5
\subsubsection{Footnotes}
The command \|\footnote| produces footnotes with reference marks such as
\footnote{An example of footnote 1.} and \footnote{An example of
footnote 2.}. When there is more than one footnote within a single
page, please note that it is necessary to run \LaTeX\ twice to process
them correctly. Moreover, it is sometimes preferable to separate a
footnote and its mark into different columns. This can be achieved
using the \|\footnotemark| and \|\footnotetext| commands. The footnote
numbering produced by \LaTeX\ is continuous throughout the paper; it
does not restart on each new page.
%4.3.6
\subsubsection{Overfulls and Underfulls}
The final result must be free from any overfulls. It is well known that
almost all overfulls can be avoided with a little effort when writing
sentences. For example, avoiding long in-text formulas and \|\verb| is
very effective. However, tricks using the \|flushleft| environment,
\|\\|, or \|\linebreak| are not recommended because they cause quite
unattractive results.
For underfulls, you will conveniently get the following warning message,
\begin{quote}\footnotesize*
\|Underfull| \|\hbox| \|(badness 10000)| \|detected|
\end{quote}
by inserting \|\\| at the end of a paragraph. This message is also
output when you use \|\\| just before a list-like environment, just
before an \|\item|, and at the end of the environment. Such underfulls
cause unattractive empty lines and a flood of warnings that will hide
important error messages.
%4.4
\subsection{Formulas}\label{sec:ITEM}
%4.4.1
\subsubsection{In-text Formulas}
In-text formulas may be surrounded by any proper math-open\slash close
pair, i.e. \|$| and \|$|, \|\(| and \|\)|, or \|\begin| and \|\end| for
the \|math| environment. Note that tall materials in in-text formulas,
such as \smash{$\frac{a}{b}$} (\|\frac{a}{b}|), are unattractive and
will disarrange the baseline progression.
%4.4.2
\subsubsection{Displayed Formulas}
Displayed formulas {\em must not be surrounded by the pair
\|$$|}. Instead, use the \|\[| and \|\]| pair or one of the environments
\|displaymath|, \|equation|, or \|eqnarray|. These commands\slash
environments indent formulas (not centered) and keep fixed baselines as
follows.
\begin{equation}
\Delta_l = \sum_{i=l+1}^L\delta_{pi}.
\end{equation}
%4.4.3
\subsubsection{Eqnarray environment}
For a sequence of two or more related formulas (equations), use the
\|eqnarray| environment to line them up at equal (or unequal) signs
instead of \|\[| \ \|\]| or the \|equation| environment.
%4.4.4
\subsubsection{Special Fonts}
It is strongly recommended to use only standard {\LaTeX} math
fonts. Otherwise, you must report that you are using special fonts.
\begin{figure}[tb]%1
\setbox0\vbox{\it
\hbox{\|\begin{figure}[tb]|}
\hbox{\quad \|<|figure-body\|>|}
\hbox{\|\caption{<|caption\|>}|}
\hbox{\|\label{| $\ldots$ \|}|}
\hbox{\|\end{figure}\|}}
\centerline{\fbox{\box0}}
\caption{Single column figure with caption\\
explicitly broken by $\backslash\backslash$}
\label{fig:single}
\end{figure}
\begin{figure}[tb]%2
\begin{minipage}[t]{0.5\columnwidth}
\footnotesize
\setbox0\vbox{
\hbox{\|\begin{minipage}[t]%|}
\hbox{\| {0.5\columnwidth}|}
\hbox{\|\captionType{table}|}
\hbox{\|\caption{| \ldots \|}|}
\hbox{\|\ecaption{| \ldots \|}|}
\hbox{\|\label{| \ldots \|}|}
\hbox{\|\makebox[\textwidth][c]{%|}
\hbox{\|\begin{tabular}[t]{lcr}|}
\hbox{\|\hline\hline|}
\hbox{\|left¢er&right\\\hline|}
\hbox{\|L1&C1&R1\\|}
\hbox{\|L2&C2&R2\\\hline|}
\hbox{\|\end{tabular}}|}
\hbox{\|\end{minipage}|}}
\hbox{}
\centerline{\fbox{\box0}}
\caption{Contents of table \protect\ref{tab:right}}
\label{fig:left}
\end{minipage}%
\begin{minipage}[t]{0.5\columnwidth}
\CaptionType{table}
\caption{A table built by Fig.\ \protect\ref{fig:left}}
\label{tab:right}
\makebox[\textwidth][c]{\begin{tabular}[t]{lcr}\hline\hline
left¢er&right\\\hline
L1&C1&R1\\
L2&C2&R2\\\hline
\end{tabular}}
\end{minipage}
\end{figure}
\begin{figure}[t]
\setbox0\vbox{\it
\hbox{\|\begin{figure}[tb]|}
\hbox{\quad \|<|figure-body\|>|}
\hbox{\|\caption{<|caption\|>}|}
\hbox{\|\label{| $\ldots$ \|}|}
\hbox{\|\end{figure}\|}}
\centerline{\fbox{\box0}}
\caption{Single column figure with caption\\
explicitly broken by $\backslash\backslash$}
\end{figure}
\begin{figure*}[t]
\setbox0\vbox{\large
\hbox{\|\begin{figure*}[t]|}
\hbox{\quad\|<|figure-body\|>|}
\hbox{\|\caption{<|caption\|>}|}
\hbox{\|\label{| $\ldots$ \|}|}
\hbox{\|\end{figure*}|}}
\centerline{\fbox{\hbox to.9\textwidth{\hss\box0\hss}}}
\caption{Double column figure}
\label{fig:double}
\end{figure*}
%4.5
\subsection{Figures}
A figure fit to one column is specified by the form shown in
\figref{fig:single}. Note that you must not specify the \|h| option.
The \|\caption| of a figure should be given below the figure body
together with a \|\label| command. A long caption will be automatically
broken into two or more lines and centered with respect to the widest
line. You can assist, however, with the line breaking by adding \|\\|
to obtain a more beautiful result, especially for two-line captions, as
shown in \figref{fig:single}.
If you want to rank two or more figures and/or tables in a \|figure| (or
\|table|) environment in order to save space, enclose each figure\slash
table and its \|\caption| in a \|minipage| environment as shown in
\figref{fig:left} and \tabref{tab:right}. Also, as in a \|figure|
environment, the caption for \tabref{tab:right} is correctly typeset
because the \|minipage| for it has the \|\captionType{table}| command to
specify the type of caption. The command can of course be used with the
\|figure| argument to give a figure caption.
\Figref{fig:double} shows how to make a double column figure.
You may use any size font, as shown in \figref{fig:double}. Also, you
may include an encapsulated PostScript file (so called EPS file) as the
body of a figure. To include, use
%
\begin{quote}
\|\usepackage{graphicx}|
\end{quote}
%
in the preamble and put the \|\includegraphics| command where you wish
to embed the EPS graphics with its file name (and options if necessary).
You might have noticed that the first reference to \figref{fig:single}
is bold-faced, while the second and third are typed in roman fonts.
This font switching is a rule of the Journal\slash Transactions and will
be automatically performed if you use \|\figref{<|label\|>}| instead of
\|Fig.~\ref{<|label\|>}|. Another rule is that ``Figure'' must be used
instead of ``Fig.''\ if the reference is the first word of a sentence,
such as was the first reference to \figref{fig:double} above.
Unfortunately, this switching is too hard to do automatically, so you
must use \|\figref{<|label\|>}| in such cases.
%4.6
\subsection{Tables}
A table with many rules is not very beautiful. \tabref{tab:example}
shows an example of a table with standard style rules. Note that the
uppermost rule is doubled, and no rules are drawn on the left and right
edges. The caption should be put above the table. The default font size
for tables is \|\footnotesize|. Any reference to a table should be made
using \|\tabref{<|label\|>}|.
\begin{table}[tb]
\caption{Sections and sub-sections in which list-like environments are used (example of table)}
\label{tab:example}
\hbox to\hsize{\hfil
\begin{tabular}{l|lll}\hline\hline
&enumerate&itemize&description\\\hline
type-1& 2 & 3 & 4.5 \\
type-2& ---& 4.11 & 4.7 \\
type-3& 2 & --- & 4.5\\
type-4& --- & 4.8 & 4.3 \\\hline
\multicolumn{4}{l}{type-1\,: {\tt enumerate}, etc.\quad
type-2\,: {\tt enumerate*}, etc.}\\
\multicolumn{4}{l}{type-3\,: {\tt Enumerate}, etc.\quad
type-4\,: {\tt ENUMERATE}, etc.}\\
\end{tabular}\hfil}
\end{table}
%4.7
\subsection{Citations, Reference, Acknowledgements}
%4.7.1
\subsubsection{Citations}
The command \|\cite| is used to add citations in the text. Cited labels
are sorted automatically and separated by using square brackets \|[ ]|.
Thus,
\begin{quote}
\|The paper \cite{companion,latex} is|\\
\|an overview of \LaTeX|.
\end{quote}
will produce
\begin{quote}
The paper \cite{companion,latex} is an overview of \LaTeX.
\end{quote}
%4.7.2
\subsubsection{List of References}
References should be arranged in alphabetical or cited order.
It is recommended to use BiB{\TeX} and style files
\|ipsjsort-e.bst|
(alphabetical order) or \|ipsjunsort-e.bst| (cited order) to make
references fit to the traditional style.
Remember that you must include \|.bbl| file in the file package, instead of
\|.bib|.
If you cannot use BiB{\TeX} and have to make references manually using the
bibliography environment, observe the references of this guide carefully
and follow its style.
%4.7.3
\subsubsection{Acknowledgments and Appendices}
If you want to acknowledge people, put your acknowledgments just before
the references and enclose them in the \|acknowledgment| environment.
Appendices, if there are any, should be put just after the references
and \|\appendix| command. Sectioning commands produces headings like
{\bf \ref{A1}}, {\bf \ref{A2}}, and so on in the appendices.
%4.8
\subsection{Biography}
Biographies of authors are positioned at the end of the document, just
before \|\end{document}|, as follows.
%
\begin{quote}
\|\begin{biography}|\\
\|\profile{<|1st-author's-name\|>}|\\
\mbox{}\quad\|{<|biography-of-1st-author\|>}|\\
\|\author{<|2nd-author's-name\|>}|\\
\mbox{}\quad\|{<|biography-of-2nd-author\|>}|\\
\mbox{}\quad $\ldots\ldots\ldots$ \\
\|\end{biography}|
\end{quote}
Generally, photographs used in author biographies should be identification photographs.
The printers will crop these photographs to a size of 30\,mm by 25\,mm.
Avoid using photographs that contain missing portions of the face or photographs
in which the outline of the face is difficult to distinguish against the background.
It is recommended to use photographs that have no background or that
have light-colored backgrounds.
When digitally submitting photographs for the author biography,
the photograph must have a resolution of at least 300\,dpi and must
have been captured using a camera with at least one megapixel resolution.
Since photographs for the author biographies will be incorporated into
digital data by the printers at the time the composition is prepared,
it is not necessary to digitally insert the photographs into the draft.
\newpage%%%
%5
\section{Check List of ``Dos and Don'ts''}
%5.1
\subsection{The basics of writing}
\begin{itemize}
\item[$\Box$] Describe a paper so that readers understand the novelty,
availability, and reliability of the research.
\item[$\Box$] Try to make a paper easy to read (discontinuity in the
story and obscure backgrounds or themes are a burden to
readers).
\item[$\Box$] Revisit the paper if the problem to be solved is not
generalized (entirely focused on a problem at XX
University, etc.) or if the paper reports deliverables
only and does not describe the problem itself.
\item[$\Box$] Rethink the paper if its conclusion is not clearly
described, it does not adequately point out its
applicability, limits, and controversial points, or its
conclusion does not follow the contents.
\item[$\Box$] Expressions that are inappropriate for scientific papers
and that are hard to understand should be reconsidered.
\item[$\Box$] Second thought is necessary if sentences are in colloquial
style.
\item[$\Box$] Check the structure of chapters and sections and the
organization of the paper.
\item[$\Box$] Do not make the paper so that grasping the meaning is
difficult without guessing from the context.
\item[$\Box$] Confirm if the explanation of the hypotheses is enough and
does not contain any gaps in meaning.
\item[$\Box$] The authors should not submit a manuscript that includes
redundant and/or too brief descriptions.
\item[$\Box$] The authors should eliminate undefined terminologies.
\end{itemize}
%5.2
\subsection{Show novelty and usefulness clearly}
\begin{itemize}
\item[$\Box$] The authors should not submit a manuscript that does not
clarify the motivation and the goal of their study and the
relationship to other existing studies.
\item[$\Box$] The authors should not submit a manuscript that does not
clarify what technologies are well/publicly known and what
idea they are newly/originally proposing.
\item[$\Box$] The authors should provide sufficient references in their
manuscript to back up the originality of their study.
\item[$\Box$] The authors should not submit a manuscript in which the
readers cannot understand their proposal (or cannot find
any originality in it) because it consists entirely of
abstractive and/or conceptual descriptions.
\item[$\Box$] The authors should not submit a manuscript that lacks
discussions on the effectiveness of their proposal.
\end{itemize}
%5.3
\subsection{Concrete attention to writing}
\begin{itemize}
\item[$\Box$] The authors should not submit a manuscript whose Japanese
title does not match its content correctly.
\item[$\Box$] The authors should not submit a manuscript whose English
title does not match its content correctly or that
contains incorrect English usage.
\item[$\Box$] The paper should be revised when its abstract does not
show its purpose or is written in inadequate English.
\item[$\Box$] The paper should be revised when symbols and abbreviations
are not popular, wordings are not adequate, or the
explanations of its pictures and tables are not adequate.
\item[$\Box$] The paper should be revised when special wordings, which
are popular only in an individual or local group or a
small company, are used without any explanations.
\item[$\Box$] The paper should be revised when its pictures or tables
are not semantically clear or they contain mistakes.
\item[$\Box$] The paper should be revised when its pictures or tables
are not visually clear.
\item[$\Box$] The paper should be revised when the size or the scale of
its pictures or tables are not adequate.
\end{itemize}
%5.4
\subsection{Regarding references}
\begin{itemize}
\item[$\Box$] The number of references should be more than 10 (Some
opinions say more than 20 or 30 in some research areas.
\item[$\Box$] A sufficient number of references are required to show the
paper's novelty.
\item[$\Box$] The paper should be revised when it has an insufficient
number of references.
\item[$\Box$] Referring to appropriate papers written by Japanese
authors contributes to the further progression of the
Japanese research community.
\item[$\Box$] Do not include self-citations excessively.
\end{itemize}
%5.5
\subsection{Double submission}
\begin{itemize}
\item[$\Box$] Double submission of the original paper is
prohibited. However, it is permissible to submit a paper
accepted at an international conference and free from
copyright issues.
\item[$\Box$] Do not use the same figures or charts already included in
other original papers, except those that have proper
citations.
\item[$\Box$] Be careful not to have overlap between the paper and other
published articles.
\end{itemize}
%5.6
\subsection{Check by other researchers}
\begin{itemize}
\item[$\Box$] Proofreading by experienced persons with many accepted
papers is strongly recommended.
\item[$\Box$] Take care to avoid leaps of logic from the viewpoint of
the readers.
\end{itemize}
%5.7
\subsection{Miscellaneous}
\begin{itemize}
\item[$\Box$] After the first review round, do not modify the paper
except for the stated conditions for acceptance without
the reviewers' approval.
\item[$\Box$] The authors cannot select reviewers.
\item[$\Box$] Fill the self-check sheet carefully before submitting the
paper.
\end{itemize}
\newpage%%
%6
\section{Concluding Remarks}
We dare not dream that the style files are perfect but rather wish to
improve them with your cooperation and hope that you will let us know of
any complaints, comments, suggestions by e-mail to:
\begin{quote}
\|editt@ipsj.or.jp|.
\end{quote}
\begin{acknowledgment}
We wrote this article based on the guideline for A4 landscape layout.
We are grateful to Prof.\ Hiroshi Nakashima from Kyoto University,
for his valuable comments on making a class-file,
and his consent to usage of BiB{\TeX} files.
We are also very thankful to the editorial committee for their
contributions in writing the guideline for the A4 landscape layout.
\end{acknowledgment}
\begin{thebibliography}{99}
\bibitem{companion}%1
Goossens, M., Mittelbach, F. and Samarin, A.:
{\it The LaTeX Companion},
Addison Wesley, Reading,
Massachusetts (1993).
\bibitem{latex}%2
Lamport, L.:
{\it A Document Preparation System {\LaTeX} User's Guide \& Reference Manual},
Addison Wesley, Reading, Massachusetts (1986).
\bibitem{article1}%3
Itoh, S. and Goto, N.:
An Adaptive Noiseless Coding for Sources with Big Alphabet Size,
{\it Trans.\ IEICE},
Vol.E74, No.9, pp.2495--2503 (1991).
\bibitem{article2}%4
Abrahamson, K., Dadoun, N., Kirkpatrick, D.G. and Przytycka, T.:
A Simple Parallel Tree Contraction Algorithm,
{\it J.\ Algorithms},
Vol.10, No.2,
pp.287--302 (1989).
\bibitem{article3}%5
Yamakami, T.: Exploratory Session Analysis in the Mobile Clickstream,
{\it IPSJ Digital Courier},
Vol.3, pp.14--20 (online), \\
\doi{10.2197/ipsjdc.3.14} (2007).
\bibitem{book1}%6
Foley, J.D. et al.:
Computer Graphics --- Principles and Practice,
System Programming Series, Addison-Wesley,
Reading, Massachusetts, 2nd edition (1990).
\bibitem{book2}%7
Chang, C.L. and Lee, R.C.T.:
Symbolic Logic and Mechanical Theorem Proving,
Academic Press, New York (1973).
\bibitem{booklet1}%8
{Institute for New Generation Computer Technology}:
Overview of the Fifth Generation Computer Project,
distributed in {FGCS'92} (1992).
(in Japanese).
\bibitem{inbook1}%9
Knuth, D.E.:
Art of Computer Programming,
{\it Fundamental Algorithms},
Vol.1, chapter 2,
pp.371--381,
Addison-Wesley, 2nd edition (1973).
\bibitem{incollection1}%10
Schwartz, A.J.:
Subdividing B{\'e}zier Curves and Surfaces,
{\it Geometric Modeling: Algorithms and New Trends\/}
(Farin, G.E., ed.),
SIAM, Philadelphia,
pp.55--66 (1987).
\bibitem{inproceedings1}%11
Baraff, D.:
Curved Surfaces and Coherence for Non-penetrating Rigid Body
Simulation,
{\it Proc.\ SIGGRAPH '90\/} (Beach, R.J., ed.),
Dallas,
Texas, ACM, Addison-Wesley,
pp.19--28 (1990).
\bibitem{inproceedings2}%12
Nakashima, H. et al.:
OhHelp: A Scalable Domain-Decomposing Dynamic Load
Balancing for Particle-in-Cell Simulations,
{\it Proc.\ Intl.\ Conf. Supercomputing},
pp.90--99 (online),\\
\doi{http://doi.acm.org/10.1145/1542275.1542293} (2009).
\bibitem{manual1}%13
Adobe Systems Inc.:
{\it PostScript Language Reference Manual},
Reading,
Massachusetts (1985).
\bibitem{mastersthesis1}%14
Ohno, K.:
Efficient Message Communication of Concurrent Logic Programming
Language KL1 Based on Static Analysis,
Master's thesis,
Dept.\ Information Science, Kyoto University (1995).
\bibitem{misc1}%15
Saito, Y. and Nakashima, H.:
{\tt ipsjpapers.sty} (1995).
(Style file for Trans. IPSJ distributed to authors.).