Skip to content

give a default value to T and convert models from v1.2#789

Merged
amcadmus merged 4 commits intodeepmodeling:develfrom
njzjz:v1.2-compatibility
Jun 27, 2021
Merged

give a default value to T and convert models from v1.2#789
amcadmus merged 4 commits intodeepmodeling:develfrom
njzjz:v1.2-compatibility

Conversation

@njzjz
Copy link
Copy Markdown
Member

@njzjz njzjz commented Jun 22, 2021

@njzjz njzjz added this to the v2.0.0 milestone Jun 22, 2021
@njzjz njzjz requested review from amcadmus and denghuilu June 22, 2021 22:54
@codecov-commenter
Copy link
Copy Markdown

codecov-commenter commented Jun 22, 2021

Codecov Report

❌ Patch coverage is 9.09091% with 30 lines in your changes missing coverage. Please review.
✅ Project coverage is 73.65%. Comparing base (4555034) to head (9f696f8).

Files with missing lines Patch % Lines
deepmd/utils/convert.py 6.89% 27 Missing ⚠️
deepmd/entrypoints/convert.py 25.00% 3 Missing ⚠️
Additional details and impacted files
@@            Coverage Diff             @@
##            devel     #789      +/-   ##
==========================================
- Coverage   74.05%   73.65%   -0.41%     
==========================================
  Files          84       84              
  Lines        6576     6619      +43     
==========================================
+ Hits         4870     4875       +5     
- Misses       1706     1744      +38     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
  • 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

@amcadmus
Copy link
Copy Markdown
Member

How about adding a section in the getting started to introduce the users the conversions of model compatibility?

(and compatability->compatibility)
@njzjz
Copy link
Copy Markdown
Member Author

njzjz commented Jun 24, 2021

I add a table to troublesome and I am not sure if it should be moved to the getting started.

@njzjz njzjz requested a review from tuoping June 24, 2021 21:05
Copy link
Copy Markdown
Collaborator

@tuoping tuoping left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

How about add a link to doc/troubleshooting/model-compatibility in getting-started?

|DeePMD-kit v1.0 | 😢 | 😄 | 😢 | 😢 | 😢 | 😢 |
|DeePMD-kit v1.1 | 😢 | 😢 | 😄 | 😢 | 😢 | 😢 |
|DeePMD-kit v1.2 | 😢 | 😢 | 😢 | 😄 | 😢 | 😢 |
|DeePMD-kit v1.3 | 😢 | 😢 | 😢 | 😊 | 😄 | 😢 |
Copy link
Copy Markdown
Member

@amcadmus amcadmus Jun 25, 2021

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Do we have tools in DeePMD-kit v1.3 to convert v1.3 model to v1.2 compatibility?

Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

No.

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

So why there is a smile? Is it a typo?

Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The smile is where model version is v1.2 and deepmd-kit version is 1.3, not converse.

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

So you mean we can convert a model v1.2 to v1.3 by using deepmd-kit v1.3. I do not see this subcommand in v1.3

Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We can convert a model v1.2 to v1.3 by using deepmd-kit v1.2. So this should be a 😢?

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yes, the manner of conversion is somewhat different... In deepmd-kit v1.2 and 1.3, it is convert-to (pending PR #631 and #633), but in v2.0 it is convert-from.

I would proposed to only keep the doc for v2.0, and write separate docs for v1.2 and 1.3, what do you think?

Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Good idea.

Copy link
Copy Markdown
Member

@denghuilu denghuilu left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

works well in my local workstation

@njzjz njzjz force-pushed the v1.2-compatibility branch from 6d9de9b to 74c8d92 Compare June 25, 2021 19:23
@amcadmus amcadmus merged commit a951d8b into deepmodeling:devel Jun 27, 2021
@njzjz njzjz deleted the v1.2-compatibility branch August 12, 2021 22:22
gzq942560379 pushed a commit to HPC-AI-Team/deepmd-kit that referenced this pull request Sep 2, 2021
)

* give a default value to T and convert models from v1.2
See also https://www.tensorflow.org/guide/create_op#backwards_compatibility.

* add documents to model compatibility

(and compatability->compatibility)

* add documentation to getting-started

* Update model-compatability.md
njzjz added a commit to njzjz/deepmd-kit that referenced this pull request Sep 21, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants