Conversation
for more information, see https://pre-commit.ci
…3/install_only
for more information, see https://pre-commit.ci
for more information, see https://pre-commit.ci
[espnet-3] Merge ESPnet master branch into espnet3 branch
… into espnet3/install_only
Espnet3/install only
- Due to the review comment for `multiple_iterator` flag, I recognized that the exception with the flag is not properly tested. I've added a new test case for this fix.
[espnet3-1] Add Data Organizer
for more information, see https://pre-commit.ci
…into espnet3/load_config
for more information, see https://pre-commit.ci
…into espnet3/load_config
for more information, see https://pre-commit.ci
for more information, see https://pre-commit.ci
for more information, see https://pre-commit.ci
sw005320
left a comment
There was a problem hiding this comment.
- Can you remove the egs directory?
- check whether some scripts are used in egs2 by using a grep for symlink
- move them in espnet2
- config files must not be used, and you can safely remove them
- Why did you change
espnet.utils-->espnet2.legacy.utils?espnet.utils.cli_utilsseems to be frequently used, and we can move this toespnet2.utils
- ditto
espnet.nets-->espnet2.legacy.nets- to remove espnet1?
espnet2.legacy.nets.pytorch_backend-->espnet2.legacy.nets(we don't need pytorch_backend
| # - name: test espnet3 integration | ||
| # run: ./ci/test_integration_espnet3.sh | ||
| # - uses: codecov/codecov-action@v2 | ||
| # with: | ||
| # flags: test_integration_espnet3 |
There was a problem hiding this comment.
Sorry, currently we don't have them. I will activate this in recipe-related PR!
There was a problem hiding this comment.
Why does this file have such a large change?
There was a problem hiding this comment.
I refactored the beam search test to use espnet2 models from using espnet-1 model. Models are built via ASRTask.build_model from espnet2, and the encoder/LM setup follows the espnet2 APIs.
| @@ -42,4 +42,4 @@ export PATH=${PYTHON_DIR}:\${PATH} | |||
| EOF | |||
|
|
|||
| . ./activate_python.sh | |||
| python3 -m pip install -U pip wheel | |||
| python3 -m pip install -U pip==25.2 wheel | |||
There was a problem hiding this comment.
Do we need this? pip==25.2
Some of them (e.g., remove |
|
I double-checked all removed Except for one known aliasing case ( All the tools and output resources are uploaded in the following gist: |
|
The pip version change (adding With pip 25.2, pip falls back to the legacy editable path (= It seems the real reason is that the I am not sure why under the current master branch it works, and in espnet3 branch it doesn't. Pinning the pip version to 25.2 is the simplest workaround for now, but if needed I would investigate the exact behavior of pip 25.3 in more detail... |
|
@Masao-Someki, Please list the TODO items (or add TODO(Nelson)) that will need attention after merging this PR.
|
|
@Fhrozen
|
|
Done! |
What did you change?
espnet2.legacy#6179Why did you make this change?
To implement ESPnet-3.
See #6133 for more details
Is your PR small enough?
No, but all changes are confirmed by reviewers, and this is a merge PR based on discussion with them.
Additional Context