Skip to content

pystiche: A Framework for Neural Style Transfer #25

@pmeier

Description

@pmeier

Submitting Author: Philip Meier (@pmeier)
All current maintainers: Philip Meier (@pmeier)
Package Name: pystiche
One-Line Description of Package: Framework for Neural Style Transfer (NST) built upon PyTorch
Repository Link: https://github.com/pystiche/pystiche
Version submitted: 0.5.0post0
Editor: @NickleDave
Reviewer 1: @edgarriba
Reviewer 2: @soumith
Archive: DOI
JOSS DOI: DOI
Version accepted: v 0.6.0
Date accepted (month/day/year): 10/08/2020


Description

pystiche is a framework for Neural Style Transfer (NST) algorithms based on PyTorch. NST is a neural-net-based technique to merge the content of one and the artistic style of another image. Similar to deep learning frameworks pystiche eases up the workflow for researchers in this field. Rather than implementing everything yourself, pystiche provides common building blocks of NST algorithms that can be conveniently combined. Thus, researchers can focus on implementing new ideas rather than implementing the periphery over and over again.

Scope

  • Please indicate which category or categories this package falls under:

    • Data retrieval
    • Data extraction
    • Data munging
    • Data deposition
    • Reproducibility
    • Geospatial
    • Education
    • Data visualization*
  • Explain how the and why the package falls under these categories (briefly, 1-2 sentences):

    pystiche can be used to reproduce NST papers while focusing on core aspects.

  • Who is the target audience and what are scientific applications of this package?

    The primary intended audience are researchers as described above. Apart from them pystiche could also be interesting for recreational use by non-scientists.

  • Are there other Python packages that accomplish the same thing? If so, how does yours differ?

    AFAIK there are no other packages provide a similar functionality. However, due to its popularity, there are many implementations, which are limited to a specific NST algorithm. An exception might be this which features the implementation of multiple papers.

  • If you made a pre-submission enquiry, please paste the link to the corresponding issue, forum post, or other discussion, or @tag the editor you contacted:

    Presubmission Inquiry: pystiche #21

Technical checks

For details about the pyOpenSci packaging requirements, see our packaging guide. Confirm each of the following by checking the box. This package:

  • does not violate the Terms of Service of any service it interacts with.
  • has an OSI approved license
  • contains a README with instructions for installing the development version.
  • includes documentation with examples for all functions.
  • contains a vignette with examples of its essential functions and uses.
  • has a test suite.
  • has continuous integration, such as Travis CI, AppVeyor, CircleCI, and/or others.

Publication options

JOSS Checks
  • The package has an obvious research application according to JOSS's definition in their submission requirements. Be aware that completing the pyOpenSci review process does not guarantee acceptance to JOSS. Be sure to read their submission requirements (linked above) if you are interested in submitting to JOSS.
  • The package is not a "minor utility" as defined by JOSS's submission requirements: "Minor ‘utility’ packages, including ‘thin’ API clients, are not acceptable." pyOpenSci welcomes these packages under "Data Retrieval", but JOSS has slightly different criteria.
  • The package contains a paper.md matching JOSS's requirements with a high-level description in the package root or in inst/.
  • The package is deposited in a long-term repository with the DOI:

Note: Do not submit your package separately to JOSS

Are you OK with Reviewers Submitting Issues and/or pull requests to your Repo Directly?

This option will allow reviewers to open smaller issues that can then be linked to PR's rather than submitting a more dense text based review. It will also allow you to demonstrate addressing the issue via PR links.

  • Yes I am OK with reviewers submitting requested changes as issues to my repo. Reviewers will then link to the issues in their submitted review.

Code of conduct

P.S. Have feedback/comments about our review process? Leave a comment here

Editor and Review Templates

Editor and review templates can be found here

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    Status

    joss-accepted

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions