Scribd
Upload
26 views

ieee-data-descriptions

Uploaded by

fopoy18823
Copyright
© © All Rights Reserved
Available Formats
Download as PDF, TXT or read online on Scribd
26 views

ieee-data-descriptions

Uploaded by

fopoy18823
Copyright
© © All Rights Reserved
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 2

Descriptor: The Name of My Dataset

(TNM)
FIRST A. AUTHOR1 , (FELLOW, IEEE), SECOND B. AUTHOR2 , AND THIRD C.
AUTHOR, JR.1,2 , (MEMBER, IEEE)
1
National Institute of Standards and Technology, Boulder, CO 80305 USA
2
Department of Physics, Colorado State University, Fort Collins, CO 80523 USA
CORRESPONDING AUTHOR: First A. Author (e-mail: [email protected]).
The authors contributed equally to this article. This work was supported by the XYZ Research Council.

ABSTRACT IEEE Data Descriptions (IEEE-DATA) Descriptor articles (the main type of article published)
describe the published (or soon-to-be-published) dataset. In essence, this is a detailed manual on the
dataset – what it is and how to use it. Each article will follow a set format for predetermined, well-defined
sections. Metadata will also be collected to further classify the data that is being described, as well as
funding sources, etc. The purpose of a Descriptor article is to: document sources and methods used to
collect the data, to quantify the quality of the data, discuss any issues and caveats with the data or use of,
discuss basic statistics about the data (e.g., collection period, location); and, collect enhanced metadata
(define each file, columns within, and row type).

For Descriptor articles the abstract is considered the Introduction section in traditional articles.
Authors can introduce the dataset by briefly introducing or describing it. Abstracts must be 150–250,
and references/citations are not allowed. They cannot claim new scientific findings or experimental
results. Articles have a recommended length of 4—8 pages. Any extra information can be submitted
as supplementary information, which will be published alongside the article on IEEE Xplore. Author
Biographies (in LaTeX the IEEEbiography) are not a part of any article type. Do not include these with
your submission. Any submission that does include author biographies will be returned to the authors and
will not be reviewed. Descriptor articles must have and only have the below sections (without numbering)
in that order.

IEEE SOCIETY/COUNCIL Power and Energy Society (PES)

DATA DOI/PID <add-your-DOI-here>

DATA TYPE/LOCATION Time-series; SFU Campuses, Metro Vancouver, Canada

INDEX TERMS Enter, keywords/phrases, alphabetically, separated, by, commas

BACKGROUND COLLECTION METHODS AND DESIGN


Background must provide an overview of the data collected Collection Methods and Design must provide details on
and discuss how it fits with other comparable, published how that data was collected. This includes details on any
datasets. Authors must make clear the data’s value and how hardware/system designs used to collect the data (i.e., data
it can be reused. Authors must also summarize any previous acquisition). In addition, the steps and procedures used to
publication made using this data with a brief summary and collect and process the data in its final form (i.e., com-
citation for each time used. DO NOT include a paragraph putational processing). It is recommended that the authors
on how your article is organized; all articles of this type are provide diagrams that show the overall system/procedure
organized the same way. used.

This work is licensed under a Creative Commons Attribution 4.0 License. For more information, see https://creativecommons.org/licenses/by/4.0/

VOLUME 00, 2024 1


Author et al.: IEEE-DATA Descriptor Article Template

files B and C plus some error terms. The format of each data
file should be sufficiently described.

INSIGHTS AND NOTES


Insights and Notes must use this section to provide details on
any caveats and special case usages with the data. Authors
can also discuss how the data can be used in other ways
that they themselves cannot experiment on. For example,
authors may have a dataset that has power meter readings
and may want to point out that the data can also be used for
general/theoretical time-series analysis.

SOURCE CODE AND SCRIPTS


Source Code and Scripts must provide details on any public
source code repositories that contain code used to collect,
clean, or process this data. Details on any third-party soft-
ware used should also be listed (including software version
FIGURE 1. Magnetization as a function of applied field. Note that “Fig.” is
abbreviated. There is a period after the figure number, followed by two numbers). URLs and links to these repositories should be
spaces. It is good practice to explain the significance of the figure in the listed in the reference section. It is recommended that
caption. these repositories have an associated DOI to ensure their
TABLE 1. Units for Magnetic Properties permanence: https://github.com/some-user/some-repo/.
Symbol Quantity Conversion from Gaussian and
ACKNOWLEDGEMENTS AND INTERESTS
CGS EMU to SI a
Special thanks to Some Company or Some Person for there
Φ magnetic flux 1 Mx → 10−8 Wb = 10−8 V·s
help on using their API.
B magnetic flux density, 1 G → 10−4 T = 10−4 Wb/m2
magnetic induction
F.A., S.A., and T.A. curated and analysed the data,
H magnetic field strength 1 Oe → 103 /(4π) A/m
and wrote parts of the manuscript. S.A. reviewed the
curation and wrote parts of the manuscript. All authors
VALIDATION AND QUALITY reviewed the manuscript.
Validation and Quality must provide details that support the
technical quality and/or accuracy of the data collected. For This work was funded by Natural Resources Canada
example, the error rate or accuracy of any hardware sensors (NRCan) under project PRJ and Natural Sciences and
used for collection. Authors should provide figures and tables Engineering Research Council of Canada (NSERC)
to support this. Discovery Grant RGPIN-20XX-YYYYY.

RECORDS AND STORAGE The article authors have declared no conflicts of interest.
Records and Storage must provide details on how the data
files are structured and how the data is stored. A table that
lists all files with summary details is recommended. For REFERENCES
example, for CSV files, a description of the columns and References must follow the standard IEEE format and use
rows of each file is needed. Additionally, details on how numbered citations. Please refer to the IEEE Reference
files relate to each other is needed, especially if there is some Guide.
hierarchical structure. For example, file A is a summation of

2 VOLUME 00, 2024

You might also like