Skip to content

Latest commit

 

History

History
139 lines (105 loc) · 5.42 KB

paper.md

File metadata and controls

139 lines (105 loc) · 5.42 KB
title tags authors affiliations date bibliography arxiv-doi
Music separation is all you need
separation
u-net
name orcid affiliation
Adrian M. Price-Whelan^[co-first author]
0000-0003-0872-7098
1, 2
name affiliation
Author Without ORCID^[co-first author]
2
name affiliation
Author with no affiliation^[corresponding author]
3
name index
Lyman Spitzer, Jr. Fellow, Princeton University
1
name index
Institution Name
2
name index
Independent Researcher
3
10 August 2021
paper.bib
10.21105/joss.01667

Abstract

The abstract should be around 250 words long as usual, and should be provided for submissions of all categories: posters, long talks and discussions.

  • Please briefly describe the particular points your submission focuses on and/or the problems it aims to solve.
  • For all categories except discussions, please also briefly summarize the contributions.

Paper structure depending on the category

Posters

In case of a poster that presents a MDX submission, please atinclude a method section, where you describe your system. It would be nice to have both explanations and at least one figure of the architecture / model / whatever you see fit.

Long talks

Long talks will use time slots of approximately 30', where the presenter will be free to either present some recent research or an overview of a topic that may be of interest to the music demixing community. You are free to present some work that was already published recently on arxiv, but this work shouldn't have been presented to a public conference already.

The architecture of the paper for this category is classical and should be self contained. The length should be around 2 pages, excluding references, but we do accept longer papers. The point is: there should be enough information for the committee to decide whether it makes sense to give you the mic for half an hour !

Ideas / Discussions

Submission from this category should include two sections:

  • A Motivations section would give some context and would explain why having participants discussing this particular topic is relevant.
  • A Questions section provides a list of the actual questionns / points that you want to raise. There should be at least around 5 of them.

Pleas note that you tacitely agree to chair to discussion if you submit in this category.

The expected length for submissions in this category is around one page, excluding references. It would be nice to have some illustration if applicable.

Example of content fitting the template

Introduction

Gala is an Astropy-affiliated Python package for galactic dynamics. Python enables wrapping low-level languages (e.g., C) for speed without losing flexibility or ease-of-use in the user-interface. The API for Gala was designed to provide a class-based and user-friendly interface to fast (C or Cython-optimized) implementations of common operations such as gravitational potential and force evaluation, orbit integration, dynamical transformations, and chaos indicators for nonlinear dynamics. Gala also relies heavily on and interfaces well with the implementations of physical units and astronomical coordinate systems in the Astropy package [@astropy] (astropy.units and astropy.coordinates).

Gala was designed to be used by both astronomical researchers and by students in courses on gravitational dynamics or astronomy. It has already been used in a number of scientific publications [@Pearson:2017] and has also been used in graduate courses on Galactic dynamics to, e.g., provide interactive visualizations of textbook material [@Binney:2008]. The combination of speed, design, and support for Astropy functionality in Gala will enable exciting scientific explorations of forthcoming data releases from the Gaia mission [@gaia] by students and experts alike.

Mathematics

Single dollars ($) are required for inline mathematics e.g. $f(x) = e^{\pi/x}$

Double dollars make self-standing equations:

$$\Theta(x) = \left{\begin{array}{l} 0\textrm{ if } x < 0\cr 1\textrm{ else} \end{array}\right.$$

You can also use plain \LaTeX for equations \begin{equation}\label{eq:fourier} \hat f(\omega) = \int_{-\infty}^{\infty} f(x) e^{i\omega x} dx \end{equation} and refer to \autoref{eq:fourier} from text.

Figures

Figures can be included like this:

Caption for example figure.{ width=40% }

and referenced from text using \autoref{fig:example}.

Acknowledgements

We acknowledge contributions from Brigitta Sipocz, Syrtis Major, and Semyeong Oh, and support from Kathryn Johnston during the genesis of this project.

References

All submissions should include a reference section.

How to cite

Citations to entries in paper.bib should be in rMarkdown format.

If you want to cite a software repository URL (e.g. something on GitHub without a preferred citation) then you can do it with the example BibTeX entry below for @fidgit.

For a quick reference, the following citation commands can be used:

  • @author:2001 -> "Author et al. (2001)"
  • [@author:2001] -> "(Author et al., 2001)"
  • [@author1:2001; @author2:2001] -> "(Author1 et al., 2001; Author2 et al., 2002)"