Leibniz Transactions on Embedded Systems, Volume 8
Leibniz Transactions on Embedded Systems, Volume 7
LITES publishes original articles on all aspects of embedded computing systems according to the principles of Open Access. The journal is published by the European Design and Automation Association (EDAA) \ EMbedded Systems Special Interest Group (EMSIG) and Schloss Dagstuhl -- Leibniz-Zentrum für Informatik GmbH, Dagstuhl Publishing
LITES aims at efficient reviewing procedures to ensure that articles are published within one year of submission. LITES is continuously open for submission.
Leibniz Transactions on Embedded Systems (LITES) aims to publish high-quality scholarly articles and to ensure efficient submission, reviewing, and publishing procedures that will result in timely publication. All articles are published open access, i.e., are accessible online at no cost to the reader. All rights are retained by the author(s).
LITES publishes original articles on all aspects of embedded computing systems.
The journal is flexible in the types of articles it publishes. The range includes (but is not limited to) regular technical papers, literature surveys, historical perspectives, position papers, tools papers, and companion papers to open-access research artifacts (such as open-source software and hardware designs, data sets, case studies, challenge problems and competitions, etc.). All contributions that advance the state of the art and/or the scientific discourse on embedded computing systems are welcome.
Topics of interest include (but are not limited to):
LITES welcomes all methods of scientific inquiry, including (but not limited to) systems building and empirical evaluation, mathematical modeling and rigorous proof, formal methods, deployment studies and reflections on “lessons learned” in practice, as well as statistical and empirical methods, surveys of industry practice, and user studies.
Schloss Dagstuhl, the publisher of LITES, charges a moderate article-processing charge (APC) of 100€ (net) upon acceptance, which typically is paid by the author or his/her institution. Authors without institutional support or facing financial hardship may apply for an APC waiver.
Schloss Dagstuhl is a publicly funded nonprofit organization. The modest APC serves to offset only the real costs incurred during the publication process and does not generate any profits.
Additionally, the first 20 accepted papers each year automatically receive a FULL APC WAIVER thanks to financial support by EMSIG.
LITES shall have an editor-in-chief and an editorial board consisting of 10 to 20 associate editors. LITES is operated not-for-profit. All editors and reviewers are unpaid volunteers. The APC is charged to compensate the real costs and can be waived in exceptional circumstances on a case-by-case basis for authors without institutional support and for who the APC would result in undue financial hardship.
Decisions are taken by the associate editor in charge of a submission. A minimum number of 3 reviews for each submissions required. The journal uses a single-anonymous peer-review process (i.e., authors do not know who the reviewers are, but reviewers do know who the authors are).
The editor-in-chief (EiC) assigns each new submission to a responsible associate editor, taking into account possible conflicts of interest (CoI), and has the final responsibility for decisions about acceptance and rejection of submissions.
The associate editors
Reviewers provide
Manuscripts are reviewed based on the following criteria:
Papers are not reviewed on their perceived significance or expected impact, which are ultimately guesswork and best left to history.
A conflict of interest (CoI) exists between a reviewer or editor and the authors if they:
Further information can be found on the Publication Ethics website of Dagstuhl Publishing.
The target timelines for handling submissions are:
Authors shall submit original work that is not submitted elsewhere while the submission and review process of LITES is going on. Authors are encouraged to submit software and data along with the article submission. This enables the replication of experiments and helps other researchers to build on the published results.
Extensions of previously published workshop and conference papers are welcome. Extensions of conference papers and workshop papers published with a DOI require at least 30% new material to be accepted. The manuscript should include a statement explaining the novel contributions on top of the preliminary conference or workshop version of the manuscript. When in doubt whether a (planned) extension meets these requirements, please inquire with the editor-in-chief for clarification.
Articles must be written in British or American English. Please be consistent – use the same form of English (i.e., British or American) throughout the text.
A submitted article shall normally be no more than 25 pages (not inclduing abstract and bibliography). Longer papers might be considered but there must be a strong justification. When planning to submit a paper significantly exceeding the 25-page limit, please reach out to the editorin-chief with a justification to obtain prior approval.
Please submit manuscripts via the LITES submission system. LITES OJS Login / LITES OJS Registration
Please download the current version of the LITES style along with an example file and detailed author instructions:
For older releases and an issue tracker, see our GitHub archive.
As part of the submission process, authors are required to check off their submission's compliance with all of the following guidelines. Submissions not adhering to these guidelines may be returned to the authors without further review.
LITES publishes original articles on all aspects of embedded computing systems according to the principles of Open Access. The journal is published by the European Design and Automation Association (EDAA) \ EMbedded Systems Special Interest Group (EMSIG) and Schloss Dagstuhl -- Leibniz-Zentrum für Informatik GmbH, Dagstuhl Publishing
LITES aims at efficient reviewing procedures to ensure that articles are published within one year of submission. LITES is continuously open for submission.
In order to do justice to the high scientific quality of the journal, which is ensured by the thorough review process, we believe that LITES articles must have an attractive and consistent layout matching the standard of the journal. Moreover, the quality of the metadata, the typesetting and the layout must also meet the requirements of other external parties such as indexing services, DOI registry, funding agencies, among others. The provided guidelines serve as the baseline for the authors, editors, and the publisher to create documents that meet as many different requirements as possible.Please comply with the following instructions when preparing your article for LITES. (See Instructions for Authors for more details.)
\section
, \subsection
, \subsubsection
, \paragraph
, \paragraph*
, and \subparagraph*
.\bibstyle{plainurl}
) for the bibliography.\hboxes
and any kind of warnings/errors with the referenced BibTeX entries.Please set the values of the metadata macros carefully since the information parsed from these macros will be passed to publication servers, catalogues and search engines. Avoid placing macros inside the metadata macros. The following metadata macros/environments are mandatory:
\title
and, in case of long titles, \titlerunning
.\author
one for each author, even if two or more authors have the same affiliation.\authorrunning
(abbreviated first names) and
\Copyright
(concatenated full author names)\ccsdesc
(ACM 2012 subject classification)\keywords
(a comma-separated list of keywords).\relatedversion
(if there is a related version, typically the "full version"); please make sure to provide a persistent URL, e.g., at arXiv.\begin{abstract}...\end{abstract}
.Generally speaking, please do not override the style defaults concerning spacing, font and color settings. To be more specific, a short checklist also used by Dagstuhl Publishing during the final typesetting is given below. In case of non-compliance with these rules, Dagstuhl Publishing will remove the corresponding parts of LaTeX code and replace it with the defaults. In serious cases, we may reject the LaTeX-source and expect the corresponding author to revise the relevant parts.
times
package is forbidden.)enumitem
and paralist
. (The enumerate package is preloaded, so you can use \begin{enumerate}[(a)]
or the like.)\noindent{\bf My Paragraph}
).\iffalse ... \fi
constructions. wrapfig
is not supported. natbib
package is not supported.) This is only a summary containing the most relevant details. Please read the complete Instructions for Authors for all details and don't hesitate to contact Dagstuhl Publishing ([email protected]) in case of questions or comments.
Didn't find what you are looking for? Don't hesitate to leave us message at [email protected]!
Please download the current version of the LITES front matter style along with an example file:
Submissions via LITES Submission System: LITES OJS Login / LITES OJS Registration
In order to satisfy the standards of our series, please note that we expect an affiliation at least to contain a city and country (for locations in the United States also the state), so we usually don't support requests asking for removing this kind of information from an affiliation.
For organizations with multiple locations please choose the location where you have been most of the time physically when carrying out this work.
We hope that our completion of affiliations according to the above criteria facilitates the contacting of authors as well as the assignment of a work to individual locations, and - last but not least - serves the harmonization of affiliations across the entire volume.
At the beginning of the submission process, the submission system has only limited information about the actual authors of the article. But on each upload, the metadata of the paper (including authors) are updated. Before the publication, the authorized users are asked to confirm (or revise, if necessary) the metadata. In more detail:
\author
macros in your file.\author
macros in your LaTeX file and do a re-upload. If the error persists, please make sure that the \author
macros are contained in the top level of your main LaTeX file (outside \if
conditionals) and contain plain data (i.e. preferably no self-defined macros).Dagstuhl Publishing uses BibTEX
to format references. Thereby the BibTEX style plainurl is used for BibTEX processing (\bibliographystyle{plainurl}
).
DOI
(preferred) or URL
natbib
package is not supported by the current styles of Dagstuhl Publishing.)
\nocite{*}
is forbidden.
bbl-file only
or an inline-bibliography
is not sufficient.
Since the automatic extraction could fail or be faulty, the final version of metadata will be extracted by the Dagstuhl Publishing Team after the typesetting is done.
In any case we ask you to confirm/correct the metadata before the work is officially published!
\relatedversion{...}
may be used to denote a related version like a full version, extended version, or also a predecessor
usually published in a reliable repository like arXiv or HAL.
As all metadata should be self-contained, please add a persistent URL, e.g. \relatedversion{A full version of the paper is available at \url{...}.}
. This also simplifies the access for all readers. Additional to the URL, you might add a reference (\cite{...}
).
Metadata should be self-contained as they are not only part of the document / PDF but also extracted and stored in a machine-readable format along with the actual document.
Please note: As hosting on a (personal or university) webpage or in cloud storage is not really sufficient for durable / persistent file storage, we highly recommend to publish your document in a reliable repository like arXiv or HAL.
Please note that a subject classification contained in your LaTeX file may be considered invalid if we cannot literally match an entry from the 2012 ACM Computing Classification System in a \ccsdesc{...}
macro in your LaTeX file. (That can have many causes.)
To save you the trouble of a new upload, please find the "Search ACM Classifications"-input field in the upload form. There you can search for the corresponding valid classification. (By using the last part of the intended classification as a search term one usually ends up with a good pre-selection.)
Note that invalid classifications will automatically be removed from the LaTeX code during the final typesetting by Dagstuhl Publishing.
If you click on "Save and Finish Author Approval", we are notified about your request.
Then we check if the proposed changes can be implemented. (Do they comply with the standards of the series? Are there no consistency issues? Are there no technical limitations, e.g. charset problems, ...).
In case these checks are positive, we implement the changes both in the metadata (if necessary) AND in the LaTeX file.
In any case, even if we cannot make the requested changes, you will be informed by E-mail.
IMPORTANT!
Please note that only minor corrections should be done at this stage. Here, "minor" also refers to the total number of changes. (We have already had inquiries with 50 change requests, most of them typos. Although each request is minor, the implementation is time-consuming in sum.) Requests that exceed our processing capacities and thus endanger the timely publication of the whole volume may be rejected.
As soon as some authorized user (usually you or your co-authors, if any) finishes the approval request and submits it to Dagstuhl Publishing (this happens at the end of Step 2), we are notified about your request.
Then we check if the proposed changes can be implemented. (Do they comply with the standards of the series? Are there no consistency issues? Are there no technical limitations, e.g. charset problems, ...).
In case these checks are positive, we implement the changes both in the metadata AND in the LaTeX file.
In any case, even if we cannot make the requested changes, you will be informed by E-mail.
The editors check everything carefully and ask for minor changes, if necessary.
When approved, the volume will be officially published.
First note that there are no automatic actions triggered when the editor submission deadline has passed! You actually decide on when to hand over the volume to Dagstuhl Publishing. (However, if you miss the deadline, we cannot guarantee a timely publication.)
Your tasks here are:
First note that the specified author submission deadline does not automatically trigger any actions (like closing the submission). However, it is the deadline communicated to the authors in E-mails generated by the system. Actually, you decide on when to close the submission manually.
The editor's tasks during paper submission are:
This macro sets the page header of odd pages, which is an abbreviated version of the concatenated author string. Sample usage:
\authorrunning{J.\,Q. Public, A.\,E. Access, and E. Example}
Please...
\,
as illustrated in the example\author
macrosDagstuhl Publishing uses BibTEX
to format references. Thereby the BibTEX style plainurl is used for BibTEX processing (\bibliographystyle{plainurl}
).
DOI
(preferred) or URL
natbib
package is not supported by the current styles of Dagstuhl Publishing.)
\nocite{*}
is forbidden.
bbl-file only
or an inline-bibliography
is not sufficient.
\ccsdesc{...}
is for classification information following the ACM 2012 Computing Classification System. Sample usage:
\ccsdesc{Theory of computation~Proof complexity} \ccsdesc{Theory of computation~Quantum complexity theory}
Please feel free to use our ACM 2012 Subject Finder to search for appropriate classifications and to generate the necessary LaTeX code.
Using this macro, you specify the copyright holder (appearing at the bottom of the title page) which is usually the team of authors. Sample usage:
\Copyright{John Q. Public, Adam E. Access, and Eve Example}
Please...
\author
macrosThis macro should be used to capture general (i.e. not author-specific) funding information.
If a funding can be clearly assigned to an author, please use the last part of the \author
macro instead.
Sample usage:
\keywords{Theory of Everything, indefinite Metrics, abstract Nonsense}
Please note:
\relatedversiondetails{...}
may be used to denote a related version like a full version, extended version, or also a predecessor
usually published in a reliable repository like arXiv or HAL. Sample usage:
\relatedversiondetails[cite={bibtex-reference}]{Full Version}{https://arxiv.org/abs/...}
As all metadata should be self-contained, please add a persistent URL to the cited version (as illustrated above). This also simplifies the access for all readers.
\supplementdetails{...}
may be used to denote supplements like related research data, source
code, posters, slides, ... hosted on a repository like zenodo, figshare, ..., Software Heritage.
Sample usage:
\supplementdetails[subcategory={Source Code}]{Software}{https://github.com/...}
The subcategory is free text, while the category (Software in the above example) must be one of the following words: Audiovisual, Collection, DataPaper, Dataset, Event, Image, InteractiveResource, Model, PhysicalObject, Service, Software, Sound, Text, Workflow, Other. (This is controlled vocabulary prescribed by our DOI provider.)
Please note: As hosting on a (personal or university) webpage or in cloud storage is not really sufficient for durable/persistent file storage, we highly recommend to publish your document in a reliable repository.
Didn't find what you are looking for? Don't hesitate to leave us message at [email protected]!