You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Since 2020 is a weird year, the plan is mainly to address a lot of the trivial issues in https://github.com/nilmtk/nilmtk/milestone/7 and release v0.5.0 after a full retest since there will be breaking changes from the dependencies, although no major changes on the NILMTK side.
v0.5.0: basic maintenance and general bugfixes. Targeting late September to late October (2020) Jan/Feb 2021. This will explicitly deprecate the code under nilmtk.legacy. Some issues listed in https://github.com/nilmtk/nilmtk/milestone/7 will probably be moved forward to v0.6 due to time constraints.
v0.6.x series: after v0.5.0, try to release a new version every month, worst case every three months. Ideally this would keep the dependencies up-to-date. Rough plan:
@PMeira , I think we also need to add a couple of examples for using the algorithms with the experimentation API and without the experimentation API.
The experimentation API sometimes restricts the users. By showing how to use the algorithms without the API might be useful as well. We need to do this in NILMTK-Contrib as well.
Since 2020 is a weird year, the plan is mainly to address a lot of the trivial issues in https://github.com/nilmtk/nilmtk/milestone/7 and release v0.5.0 after a full retest since there will be breaking changes from the dependencies, although no major changes on the NILMTK side.
September to late October (2020)Jan/Feb 2021. This will explicitly deprecate the code undernilmtk.legacy
. Some issues listed in https://github.com/nilmtk/nilmtk/milestone/7 will probably be moved forward to v0.6 due to time constraints.nilmtk.legacy
, add new datasets, address other NILM methods which cannot be easilly.Everything should be reevaluated by January/2021 for a more concrete plan of future versions.
The text was updated successfully, but these errors were encountered: