Skip to content
GitLab
Explore
Sign in
Register
Primary navigation
Search or go to…
Project
F
fluiddyn_papers
Manage
Activity
Members
Labels
Plan
Issues
Issue boards
Milestones
Wiki
Code
Merge requests
Repository
Branches
Commits
Tags
Repository graph
Compare revisions
Snippets
Build
Pipelines
Jobs
Pipeline schedules
Artifacts
Deploy
Releases
Container Registry
Model registry
Operate
Environments
Monitor
Incidents
Service Desk
Analyze
Value stream analytics
Contributor analytics
CI/CD analytics
Repository analytics
Model experiments
Help
Help
Support
GitLab documentation
Compare GitLab plans
Community forum
Contribute to GitLab
Provide feedback
Terms and privacy
Keyboard shortcuts
?
Snippets
Groups
Projects
Show more breadcrumbs
fluiddyn
fluiddyn_papers
Commits
5f9e394b
Commit
5f9e394b
authored
8 years ago
by
Pierre Augier
Browse files
Options
Downloads
Patches
Plain Diff
Change Latex to remove warnings.
parent
035bda19
No related branches found
Branches containing commit
No related tags found
Tags containing commit
No related merge requests found
Changes
3
Hide whitespace changes
Inline
Side-by-side
Showing
3 changed files
Makefile
+16
-0
16 additions, 0 deletions
Makefile
fluiddyn_paper.tex
+57
-25
57 additions, 25 deletions
fluiddyn_paper.tex
jors.cls
+7
-3
7 additions, 3 deletions
jors.cls
with
80 additions
and
28 deletions
Makefile
0 → 100644
+
16
−
0
View file @
5f9e394b
name
:=
fluiddyn_paper
.PHONY
:
all clean
all
:
$(name).pdf
clean
:
rm
-f
*
.log
*
.aux
*
.out
*
.bbl
*
.blg
*
.tmp
cleanall
:
clean
rm
-f
$(
name
)
.pdf
$(name).pdf
:
$(name).tex
pdflatex
$(
name
)
.tex
if
[
`
grep
"Package rerunfilecheck Warning: File"
$(
name
)
.log |
wc
-l
`
!=
0
]
;
then
pdflatex
$(
name
)
.tex
;
fi
This diff is collapsed.
Click to expand it.
fluiddyn_paper.tex
+
57
−
25
View file @
5f9e394b
...
...
@@ -28,12 +28,14 @@
\section*
{
Title
}
\textcolor
{
blue
}{
The title of the software paper should focus on the software,
e.g. “Text mining software from the X project”. If the software is closely
linked to a specific research paper, then “Software from Paper Title” is
appropriate. The title should be factual, relating to the functionality of the
software and the area it relates to rather than making claims about the
software, e.g. “Easy-to-use”.
}
% \textcolor{blue}{The title of the software paper should focus on the software,
% e.g. “Text mining software from the X project”. If the software is closely
% linked to a specific research paper, then “Software from Paper Title” is
% appropriate. The title should be factual, relating to the functionality of the
% software and the area it relates to rather than making claims about the
% software, e.g. “Easy-to-use”.}
FluidDyn: an open-source suite for fluid dynamics with Python
\section*
{
Paper Authors
}
...
...
@@ -37,7 +39,16 @@
\section*
{
Paper Authors
}
\textcolor
{
blue
}{
1. Last name, first name; (Lead/corresponding author first)
\\
2. Last name, first name; etc.
}
% \textcolor{blue}{1. Last name, first name; (Lead/corresponding author first) \\
% 2. Last name, first name; etc.}
1. AUGIER Pierre
$^
a
$
\\
2. BONAMY Cyrille
$^
a
$
\\
3...
\smallskip
$^
a
$
LEGI
\section*
{
Paper Author Roles and Affiliations
}
...
...
@@ -42,7 +53,11 @@
\section*
{
Paper Author Roles and Affiliations
}
\textcolor
{
blue
}{
1. First author role and affiliation
\\
2. Second author role and affiliation etc.
}
% \textcolor{blue}{1. First author role and affiliation \\
% 2. Second author role and affiliation etc.}
1. LEGI
\\
2. LEGI
\section*
{
Abstract
}
...
...
@@ -50,9 +65,18 @@
described: what problem the software addresses, how it was implemented and
architected, where it is stored, and its reuse potential.
}
FluidDyn is a project to foster open-source with Python in the fluid dynamics
community. A set of Python packages forms a framework to study fluid dynamics
with different methods, like laboratory experiments, simulations and data
processing. We first list the specialized packages of the project and then
focus on the base package called fluiddyn, which contains basic tools used in
the specialized packages.
\section*
{
Keywords
}
\textcolor
{
blue
}{
keyword 1; keyword 2; etc.
\\
Keywords should make it easy to identify who and what the software will be
useful for.
}
...
...
@@ -53,9 +77,12 @@
\section*
{
Keywords
}
\textcolor
{
blue
}{
keyword 1; keyword 2; etc.
\\
Keywords should make it easy to identify who and what the software will be
useful for.
}
Fluid dynamics research with Python. Modular, object-oriented, collaborative,
tested, documented, free and open-source software.
\section*
{
Introduction
}
\textcolor
{
blue
}{
An overview of the software, how it was produced, and the
...
...
@@ -63,6 +90,9 @@
articles. A short comparison with software which implements similar
functionality should be included in this section.
}
\section*
{
Implementation and architecture
}
\textcolor
{
blue
}{
How the software was implemented, with details of the
...
...
@@ -127,5 +157,5 @@
\item
[Date published:]
\textcolor
{
blue
}{
dd/mm/yy
}
\end{description}
{
\bf
Emulation environment
}
\textcolor
{
blue
}{
(if appropriate)
}
%
{\bf Emulation environment} \textcolor{blue}{(if appropriate)}
...
...
@@ -131,10 +161,10 @@
\begin{description}
[noitemsep,topsep=0pt]
\item
[Name:]
\textcolor
{
blue
}{
The name of the archive.
}
\item
[Persistent identifier:]
\textcolor
{
blue
}{
e.g. DOI, handle, PURL, etc.
}
\item
[Licence:]
\textcolor
{
blue
}{
Open license under which the software is licensed.
}
\item
[Date published:]
\textcolor
{
blue
}{
dd/mm/yy
}
\end{description}
%
\begin{description}[noitemsep,topsep=0pt]
%
\item[Name:] \textcolor{blue}{The name of the archive.}
%
\item[Persistent identifier:] \textcolor{blue}{e.g. DOI, handle, PURL, etc.}
%
\item[Licence:] \textcolor{blue}{Open license under which the software is licensed.}
%
\item[Date published:] \textcolor{blue}{dd/mm/yy}
%
\end{description}
\section*
{
Language
}
...
...
@@ -163,14 +193,16 @@
\section*
{
Competing interests
}
\textcolor
{
blue
}{
If any of the authors have any competing interests then these
must be declared. The authors’ initials should be used to denote differing
competing interests. For example: “BH has minority shares in [company name],
which part funded the research grant for this project. All other authors have
no competing interests."
%
If there are no competing interests, please add the statement: “The authors
declare that they have no competing interests.”
}
% \textcolor{blue}{If any of the authors have any competing interests then these
% must be declared. The authors’ initials should be used to denote differing
% competing interests. For example: “BH has minority shares in [company name],
% which part funded the research grant for this project. All other authors have
% no competing interests."
% %
% If there are no competing interests, please add the statement: “The authors
% declare that they have no competing interests.” }
The authors declare that they have no competing interests.
\section*
{
References
}
...
...
This diff is collapsed.
Click to expand it.
jors.cls
+
7
−
3
View file @
5f9e394b
%% Journal of Open Research Software Latex template -- Created By Stephen Bonner and John Brennan, Durham Universtiy, UK.
\NeedsTeXFormat
{
LaTeX2e
}
\ProvidesClass
{
jo
s
r
}
[2016/03/08 Journal Of Open Software Research]
\ProvidesClass
{
jor
s
}
[2016/03/08 Journal Of Open Software Research]
%% Article options
\DeclareOption
{
12pt
}{
...
...
@@ -33,7 +33,8 @@
\RequirePackage
{
xcolor
}
\RequirePackage
{
sectsty
}
\RequirePackage
{
enumitem
}
\RequirePackage
{
hyperref
}
% http://tex.stackexchange.com/questions/301669
\RequirePackage
[pageanchor=false]
{
hyperref
}
\RequirePackage
{
fancyhdr
}
\RequirePackage
{
titlesec
}
...
...
@@ -49,7 +50,10 @@
\pagenumbering
{
gobble
}
%% Set the font too 13 for the titles
\sectionfont
{
\fontsize
{
13
}{
15
}
\selectfont
}
% \sectionfont{\fontsize{13}{15}\selectfont}
% pa: this is not possible...
% http://tex.stackexchange.com/questions/58087/
%% Set indentation for the lists
\setlist
[description]
{
leftmargin=1cm,labelindent=1cm
}
...
...
This diff is collapsed.
Click to expand it.
Preview
0%
Loading
Try again
or
attach a new file
.
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Save comment
Cancel
Please
register
or
sign in
to comment