# \[ANN\] Julia Special Issue in Advances in Engineering Software

**URL:** <https://discourse.julialang.org/t/ann-julia-special-issue-in-advances-in-engineering-software/11874>\
**Category:** Community\
**Tags:** announcement\
**Created:** [June 21, 2018, 9:57pm UTC](https://discourse.julialang.org/t/ann-julia-special-issue-in-advances-in-engineering-software/11874 "2018-06-21T21:57:07Z")\
**Posts on this page:** 15\
**Page:** 1

<div class="post-metadata">

**Author:** ![PetrKryslUCSD](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/petrkryslucsd/32/215825_2.png) [@PetrKryslUCSD](https://discourse.julialang.org/u/PetrKryslUCSD)\
**Post date:** [June 21, 2018, 9:57pm UTC](https://discourse.julialang.org/t/ann-julia-special-issue-in-advances-in-engineering-software/11874/1 "2018-06-21T21:57:07Z")

</div>

The [Julia special issue](https://discourse.julialang.org/t/special-issue-on-julia/6839) in the [Advances in Engineering Software Journal](https://www.sciencedirect.com/journal/advances-in-engineering-software) (Elsevier) is now open for submission.

The timing is as follows:

Open submission portal 21-June-2018.  
Submission deadline 15-October-2018.  
Acceptance deadline 15-March-2019.

If you’d like to see samples of the publications in special issues, follow [this link](https://www.journals.elsevier.com/advances-in-engineering-software/special-issues), and in particular the [exascale computing special issue](https://www.sciencedirect.com/journal/advances-in-engineering-software/vol/111) may be of interest.

The manuscript should be submitted through the [regular portal](https://www.evise.com/profile/api/navigate/ADES). Please select the “VSI: JULIA2018” special issue from the drop-down list.  
 ![image](https://global.discourse-cdn.com/julialang/original/3X/2/e/2e39b5a093f04f1481a73b5354069a3d8a1939f5.png)

Please note that I will not serve as the editor (in order to avoid any suspicion of conflict of interest), but I will be asked by the editor to suggest referees for the manuscripts.

I did previously request letters of intent (also known as “very brief abstracts”) to gain a general idea of the layout of the special issue, but no one is prevented in any way from submitting a manuscript even if they did not previously expressed interest in doing so.

Please don’t hesitate to contact me if you need any information concerning this special issue.

---

<div class="post-metadata">

**Author:** ![fredrikekre](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/fredrikekre/32/1688_2.png) [@fredrikekre](https://discourse.julialang.org/u/fredrikekre)\
**Post date:** [June 21, 2018, 10:55pm UTC](https://discourse.julialang.org/t/ann-julia-special-issue-in-advances-in-engineering-software/11874/2 "2018-06-21T22:55:56Z")

</div>

In the spirit of Open Source, perhaps it would be good to share what it would cost authors to publish with Open Access, and what the consequences of not paying will be?

---

<div class="post-metadata">

**Author:** ![PetrKryslUCSD](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/petrkryslucsd/32/215825_2.png) [@PetrKryslUCSD](https://discourse.julialang.org/u/PetrKryslUCSD)\
**Post date:** [June 21, 2018, 11:11pm UTC](https://discourse.julialang.org/t/ann-julia-special-issue-in-advances-in-engineering-software/11874/3 "2018-06-21T23:11:32Z")

</div>

Fredrik,

That is a very good point. The details are laid out [here](https://www.elsevier.com/journals/advances-in-engineering-software/0965-9978/open-access-options). Let me just say that the “Gold” open access will not be cheap. But, after an initial embargo, the “Green” open access is also possible.

However, in the spirit of the Julia language, there is nothing to prevent the authors from **developing their special-issue contributions on Github**! In that way, both the source text and the source code will be open access by default. (The author should not post the final typeset version of the manuscript as printed by the Journal, unless open access has been paid for.)

---

<div class="post-metadata">

**Author:** ![dlfivefifty](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/dlfivefifty/32/1959_2.png) [@dlfivefifty](https://discourse.julialang.org/u/dlfivefifty)\
**Post date:** [June 22, 2018, 7:28pm UTC](https://discourse.julialang.org/t/ann-julia-special-issue-in-advances-in-engineering-software/11874/4 "2018-06-22T19:28:44Z")

</div>

I like this. Write papers on Github, anyone with a merged PR can be a coauthor. 🙂

---

<div class="post-metadata">

**Author:** ![PetrKryslUCSD](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/petrkryslucsd/32/215825_2.png) [@PetrKryslUCSD](https://discourse.julialang.org/u/PetrKryslUCSD)\
**Post date:** [June 24, 2018, 7:16am UTC](https://discourse.julialang.org/t/ann-julia-special-issue-in-advances-in-engineering-software/11874/5 "2018-06-24T07:16:33Z")

</div>

Interesting idea! If the PR is substantial, the author might consider co-authorship I am sure…

---

<div class="post-metadata">

**Author:** ![vchuravy](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/vchuravy/32/8_2.png) [@vchuravy](https://discourse.julialang.org/u/vchuravy)\
**Post date:** [June 28, 2018, 2:57pm UTC](https://discourse.julialang.org/t/ann-julia-special-issue-in-advances-in-engineering-software/11874/6 "2018-06-28T14:57:14Z")

</div>



---

<div class="post-metadata">

**Author:** ![chakravala](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/chakravala/32/6832_2.png) [@chakravala](https://discourse.julialang.org/u/chakravala)\
**Post date:** [August 9, 2018, 9:03am UTC](https://discourse.julialang.org/t/ann-julia-special-issue-in-advances-in-engineering-software/11874/7 "2018-08-09T09:03:38Z")

</div>

I’m planning on not only publishing the source for my article, but I will also make it available in a new research collaboration database format which I am creating in Julia. This was described earlier

> [@Citations in docs](https://discourse.julialang.org/t/citations-in-docs/5066/30):
>
> Somewhat tangentially related: I am currently creating a package that will allow people to maintain a database of LaTeX notes, and the Julia package will automatically be able to parse this database of LaTeX notes to extract citations, references, and it will allow authors to generate graph diagrams depicting the inter-relationship and dependencies of definitions, theorems, calculations, references, and results. It might be possible to substitute it in place of a docs system in the future, but f…

This is going to be a LaTeX-based research tool that can be used from the Julia REPL to dynamically edit and generate reports, books, documents, lecture notes, etc. It is going to be the first research paper assembled using this new database format, based on a maintained collection of typeset “vertices.”

---

<div class="post-metadata">

**Author:** ![PetrKryslUCSD](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/petrkryslucsd/32/215825_2.png) [@PetrKryslUCSD](https://discourse.julialang.org/u/PetrKryslUCSD)\
**Post date:** [October 10, 2018, 6:04pm UTC](https://discourse.julialang.org/t/ann-julia-special-issue-in-advances-in-engineering-software/11874/8 "2018-10-10T18:04:03Z")

</div>

Special issue on Julia deadline: I am trying to get an extension of the deadline (which currently stands at October 15). I am mildly optimistic, but please don’t rely on it at the moment. Try to get it in by the deadline, there’s always the possibility of revising slightly during the review process as manuscripts get rarely accepted without change.

---

<div class="post-metadata">

**Author:** ![JeffreySarnoff](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/jeffreysarnoff/32/1980_2.png) [@JeffreySarnoff](https://discourse.julialang.org/u/JeffreySarnoff)\
**Post date:** [October 10, 2018, 11:18pm UTC](https://discourse.julialang.org/t/ann-julia-special-issue-in-advances-in-engineering-software/11874/9 "2018-10-10T23:18:25Z")

</div>

What LaTeX package[s] do they prefer for small sections of code that appear within an article?

---

<div class="post-metadata">

**Author:** ![PetrKryslUCSD](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/petrkryslucsd/32/215825_2.png) [@PetrKryslUCSD](https://discourse.julialang.org/u/PetrKryslUCSD)\
**Post date:** [October 11, 2018, 1:17am UTC](https://discourse.julialang.org/t/ann-julia-special-issue-in-advances-in-engineering-software/11874/10 "2018-10-11T01:17:56Z")

</div>

Can’t go wrong by following [Guide for authors - Advances in Engineering Software - ISSN 0965-9978](https://www.elsevier.com/journals/advances-in-engineering-software/0965-9978/guide-for-authors)

---

<div class="post-metadata">

**Author:** ![chakravala](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/chakravala/32/6832_2.png) [@chakravala](https://discourse.julialang.org/u/chakravala)\
**Post date:** [October 11, 2018, 1:27am UTC](https://discourse.julialang.org/t/ann-julia-special-issue-in-advances-in-engineering-software/11874/11 "2018-10-11T01:27:21Z")

</div>

My paper requires

```nohighlight
\usepackage{stmaryrd}
\RequirePackage{luatex85}
\usetikzlibrary{graphs}
\usetikzlibrary{graphdrawing}
\usegdlibrary{layered}

```

because I have some tikz diagrams for AST in there, hopefully that won’t cause any issues…

---

<div class="post-metadata">

**Author:** ![PetrKryslUCSD](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/petrkryslucsd/32/215825_2.png) [@PetrKryslUCSD](https://discourse.julialang.org/u/PetrKryslUCSD)\
**Post date:** [October 11, 2018, 1:38am UTC](https://discourse.julialang.org/t/ann-julia-special-issue-in-advances-in-engineering-software/11874/12 "2018-10-11T01:38:27Z")

</div>

The review is done on PDF, but after the review if nothing else works you could convert the figures to PDF from your source…

---

<div class="post-metadata">

**Author:** ![ChrisRackauckas](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/chrisrackauckas/32/77_2.png) [@ChrisRackauckas](https://discourse.julialang.org/u/ChrisRackauckas)\
**Post date:** [October 11, 2018, 5:09am UTC](https://discourse.julialang.org/t/ann-julia-special-issue-in-advances-in-engineering-software/11874/13 "2018-10-11T05:09:59Z")

</div>

> [@JeffreySarnoff](#):
>
> What LaTeX package[s] do they prefer for small sections of code that appear within an article?

They have no format requirement for the submission, only on the re-submissions. I quite like this policy!

---

<div class="post-metadata">

**Author:** ![PetrKryslUCSD](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/petrkryslucsd/32/215825_2.png) [@PetrKryslUCSD](https://discourse.julialang.org/u/PetrKryslUCSD)\
**Post date:** [October 11, 2018, 8:06pm UTC](https://discourse.julialang.org/t/ann-julia-special-issue-in-advances-in-engineering-software/11874/14 "2018-10-11T20:06:18Z")

</div>

So the few days of extension on the October 15 deadline is apparently not a problem (according to the editor-in-chief). Please don’t overdo it though.

---

<div class="post-metadata">

**Author:** ![JeffreySarnoff](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/jeffreysarnoff/32/1980_2.png) [@JeffreySarnoff](https://discourse.julialang.org/u/JeffreySarnoff)\
**Post date:** [October 11, 2018, 8:26pm UTC](https://discourse.julialang.org/t/ann-julia-special-issue-in-advances-in-engineering-software/11874/15 "2018-10-11T20:26:00Z")

</div>

Two worked for Dr. Seuss:

> 1 fish, 2 fish, red fish blue fish

.