Update LIFL Documentation #614
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
- Added documentation for running LIFL on an external drive
Author
|
This PR fixes issue #613 |
myungjin
reviewed
Dec 12, 2024
|
|
||
| logger.debug("channel leave completed gracefully") | ||
|
|
||
| # def leave(self, channel) -> None: |
Contributor
There was a problem hiding this comment.
Can you please remove these commented lines?
Contributor
|
@ShixiongQi For your attention. |
Collaborator
I will take a look |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
This PR is to update the LIFL's documentation, including how to setup the environment and deps. This PR also includes several minor fixes on dependency issue caused by pip update and also documentation on how to run the
coord_hier_syncfl_mnistexample.Also added doc on how to install dependencies on a /mnt/ drive
Note that by not including a description, you are asking reviewers to do extra work to understand the context of this
change, which may lead to your PR taking much longer to review, or result in it not being reviewed at all.
Type of Change
Checklist