GithubHelp home page GithubHelp logo

capital-cost-recovery's People

Contributors

cristinaenache avatar danielbunn avatar elkeasen avatar jdebacker avatar peter-metz avatar

Stargazers

 avatar  avatar  avatar

Watchers

 avatar  avatar  avatar  avatar

capital-cost-recovery's Issues

PSL Criteria Checklist

The PSL appreciates the willingness of the capital-cost-recovery maintainers to join the Library! The capital-cost-recovery model is currently a PSL-incubating model. This issue highlights and provides a status update on progress towards the model obtaining PSL-cataloged status. The criteria for inclusion in the PSL catalog is outlined below, with notes on the status of this model's progress towards satisfying these criteria.

Once all "MUST" items are checked off, a PR will be opened to include a PSL_catalog.json configuration file in this repository.

Acceptance Criteria for Transparency and Quality

  • Models MUST be released under an OSI-approved open source license or the Creative Commons Public Domain Dedication (CC0).
  • Data MUST be publicly available, unless release is restricted by a third party.
    • Source data linked and available in repository.
  • For any data that SHOULD not be disclosed, provided MUST be:
    • A complete descriptive list of all data variables;
    • Descriptive statistics for all data variables for such data (including averages, standard deviations, number of observations, and correlations to other variables), to the extent that the descriptive statistics do not violate the rule against disclosure;
    • Contact information for the individual or entity who has unrestricted access to the data.
    • A complete descriptive list of all data variables;
    • Descriptive statistics for all data variables for such data (including averages, standard deviations, number of observations, and correlations to other variables), to the extent that the descriptive statistics do not violate the rule against disclosure;
    • Contact information for the individual or entity who has unrestricted access to the data.
      • All data seem available
  • Projects MUST have unit tests and SHOULD report code coverage.
  • At least one test MUST generate key outputs from source materials, the test MUST be run with every new version, and the outputs of the test MUST be checked into the repository.
  • Projects MUST report names and contact information for at least one maintainer.
  • Projects MUST have a suggested citation.
  • Projects MUST have a project overview.
    • See README
  • Projects MUST have installation directions.
  • Project MUST be mirrored in the same GitHub organization as PSL, and therefore they MUST be under version control.
  • Projects MUST use a consistent versioning scheme, which SHOULD be semantic versioning.

Community Criteria

  • Projects SHOULD have a public roadmap.
  • Projects SHOULD have contributor documentation and guidelines.
  • Projects SHOULD have regular office hours, webinars, or standing meetings.
  • Projects SHOULD list technical contributors.
  • Projects SHOULD list funders.
  • Projects SHOULD list user citations and case studies.
  • Projects SHOULD include subject matter tags, choosing from ...
  • Projects SHOULD include a disclaimer.
  • Projects SHOULD have a public issues tracker.
  • Projects SHOULD have a changelog.
  • Projects MAY have a Stack Overflow channel.
  • Projects MAY include a "News" translation of the changelog for users.
  • Projects MAY include criteria for participating in cross-model PSL initiatives.
  • Projects MAY include a link to a webapp version.
  • Projects MAY include a list of consultants.

Interoperability Criteria

  • The source code SHOULD be written in an open source language.
    • R
  • A PSL_catalog.json configuration file to be used for cataloging these criteria MUST be included in the project's repository. Specific instructions for creating this file can be found in the Catalog-Builder Documentation.

cc @elkeasen @danielbunn

Question about capital cost recovery methods

Two of the capital-cost-recovery methods described in README.md are not totally clear to me and I am not familiar enough with methods across the OECD to infer what is correct:

  1. "SL2 - Straight-Line Method with Changing Rates": Does this represent rates that are known to change ahead of time (e.g., a firm makes an investment knowing they can recover 20% of the cost for the first two years and then 10% of the cost after that time (until the item is full depreciated)) or does this method reflect ex-post rate changes (e.g., a firm made and investment in year t under tax law that allowed one to depreciate the asset under a SL method at 20% per year, but a law change at t+k only allows SL at 10% per year (and investments already in place were not grandfathered)?
  2. "InitialDB - Declining-Balance Method with an Initial Allowance": Is this method the same as DB with bonus depreciation?

If I've missed a document that outlines the equations underlying these methods, please point me towards that. I can see equations in the R code, but wanted to understand them conceptually rather than work backwards from the source code.

Thanks!

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    ๐Ÿ–– Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. ๐Ÿ“Š๐Ÿ“ˆ๐ŸŽ‰

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google โค๏ธ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.