Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Docs/#1 english document #20

Merged
merged 63 commits into from
Nov 4, 2022
Merged

Docs/#1 english document #20

merged 63 commits into from
Nov 4, 2022

Conversation

hayato-m126
Copy link
Collaborator

@hayato-m126 hayato-m126 commented Oct 24, 2022

Types of PR

  • New Features

Description

  • add English document

How to review this PR

mkdocs serve
# then access to localhost:8000

Others

closes: #1

@hayato-m126 hayato-m126 requested a review from a team October 25, 2022 05:13
@kielczykowski-rai
Copy link
Contributor

I will review the PR today 👀

Copy link
Contributor

@kielczykowski-rai kielczykowski-rai left a comment

Choose a reason for hiding this comment

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

Most of the changes are rather stylistic, but I leave the final decision to include them in the repository to you. The documentation is extensive, and I proposed some improvements which I hope will contribute to better reception of the tool and documentation itself. 🙇‍♂️

I know there are a lot of comments, but it is possible to include all the wanted changes in one commit by using the Add suggestion to batch option on GitHub.

docs/index.en.md Outdated Show resolved Hide resolved
docs/index.en.md Outdated Show resolved Hide resolved
docs/introduction/index.en.md Outdated Show resolved Hide resolved
docs/introduction/index.en.md Outdated Show resolved Hide resolved
docs/introduction/overview.en.md Outdated Show resolved Hide resolved
docs/use_case/performance_diag.en.md Outdated Show resolved Hide resolved
docs/use_case/performance_diag.en.md Outdated Show resolved Hide resolved
docs/use_case/performance_diag.en.md Outdated Show resolved Hide resolved
docs/use_case/performance_diag.en.md Outdated Show resolved Hide resolved
docs/use_case/performance_diag.en.md Outdated Show resolved Hide resolved
@hayato-m126
Copy link
Collaborator Author

Thanks for the review.
I will check the suggested revisions.

hayato-m126 and others added 3 commits October 28, 2022 14:09
markdown style: "code", "emphasis"
correct grammar errors

Co-authored-by: Michał Kiełczykowski <88498438+kielczykowski-rai@users.noreply.github.com>
Co-authored-by: Michał Kiełczykowski <88498438+kielczykowski-rai@users.noreply.github.com>
Copy link
Contributor

@kielczykowski-rai kielczykowski-rai left a comment

Choose a reason for hiding this comment

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

I have re-reviewed the PR. All changes seem to be reasonable.

I left a couple of conversations unresolved to attract attention to the Quick Demo section, which you proposed to be implemented.

@hayato-m126
Copy link
Collaborator Author

@kielczykowski-rai

I have ported the documentation that I had already submitted to autoware-documentation to this repository.

https://github.com/tier4/driving_log_replayer/tree/docs/%231-english-document/docs/quick_start

The PR for autoware-doucmentaiton is now just a link to this repository.

https://github.com/autowarefoundation/autoware-documentation/pull/217/files

@hayato-m126
Copy link
Collaborator Author

The content that was created for autoware-documentation was added as quick_start.
This has changed the chapter structure.

  1. index
  2. quick_start
  3. overview
  4. scenario_format
  5. result_format
  6. use_case

Copy link
Contributor

@kielczykowski-rai kielczykowski-rai left a comment

Choose a reason for hiding this comment

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

I have tested the example autoware use case once again and have left some comments regarding the execution of the commands in setup.

I have run the localization evaluation example, and the Tests seem to fail. The produced result can be found below:

<< show test result >>
test case 1 / 1 : use case: sample
--------------------------------------------------
TestResult: Failed
ReliabilityError: Convergence: NotTested Reliability: NVTL Sequential NG Count: 10 (Total Test: 256)

The same maps as in planning-simulation are used, so if you have already downloaded them, you do not need to do this step.

```bash
gdown -O ~/autoware_map/sample-map-planning.zip 'https://docs.google.com/uc?export=download&id=1499_nsbUbIeturZaDj7jhUownh5fvXHd'
Copy link
Contributor

Choose a reason for hiding this comment

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

this command assumes that the ~/autoware_map directory exists when downloading the file. Please mention it above the commands or add mkdir ~/autoware_map command before

Copy link
Collaborator Author

Choose a reason for hiding this comment

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

The driving_log_replayer tutorial uses the same dataset, so this step is not necessary if you have already downloaded it from other evaluation.

```bash
gdown -O ~/driving_log_replayer_data/sample_dataset.tar.zst 'https://docs.google.com/uc?export=download&id=1UjMWZj5Yc55O7BZiGHa0ikZGhwmcfPiS'
Copy link
Contributor

Choose a reason for hiding this comment

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

this command assumes that the ~/driving_log_replayer_data directory exists when downloading the file. Please mention it above the commands or add mkdir ~/driving_log_replayer_data command before

  • this google drive hyperlink seems not to download the actual file. It is empty in my case. I needed to download it manually through web browser

Copy link
Collaborator Author

Choose a reason for hiding this comment

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

Copy link
Collaborator Author

@hayato-m126 hayato-m126 Nov 4, 2022

Choose a reason for hiding this comment

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

I think you may have been caught in google drive's daily api limit.

When I ran it in my environment it worked correctly as follows.
11/4 2:55 UTC

❯ gdown -O ~/driving_log_replayer_data/sample_dataset.tar.zst 'https://docs.google.com/uc?export=download&id=1UjMWZj5Yc55O7BZiGHa0ikZGhwmcfPiS'
Downloading...
From: https://docs.google.com/uc?export=download&id=1UjMWZj5Yc55O7BZiGHa0ikZGhwmcfPiS
To: /home/hyt/driving_log_replayer_data/sample_dataset.tar.zst
100%|██████████████████████████████████████| 3.28G/3.28G [01:38<00:00, 33.2MB/s]

docs/quick_start/setup.en.md Show resolved Hide resolved
docs/quick_start/installation.en.md Outdated Show resolved Hide resolved
hayato-m126 and others added 4 commits November 4, 2022 11:49
Co-authored-by: Michał Kiełczykowski <88498438+kielczykowski-rai@users.noreply.github.com>
Co-authored-by: Michał Kiełczykowski <88498438+kielczykowski-rai@users.noreply.github.com>
@hayato-m126
Copy link
Collaborator Author

@kielczykowski-rai
Thank you for reporting.

<< show test result >>
test case 1 / 1 : use case: sample
--------------------------------------------------
TestResult: Failed
ReliabilityError: Convergence: NotTested Reliability: NVTL Sequential NG Count: 10 (Total Test: 256)

This result happens when ndt is not convered.
This can be caused by CPU load conditions or other reasons.

In this case, you will see the following warning in the terminal.

[ndt_scan_matcher-36] [WARN] [1667540698.508454926] [localization.pose_estimator.ndt_scan_matcher]: Nearest Voxel Transformation Likelihood is below the threshold. Score: 1.840985, Threshold: 2.300000
[ndt_scan_matcher-36] [WARN] [1667540698.508579569] [localization.pose_estimator.ndt_scan_matcher]: Not Converged

I built the latest versions of galactic and humble in my environment to check the operation, and it was working fine.

@hayato-m126 hayato-m126 merged commit fc10331 into develop Nov 4, 2022
@hayato-m126 hayato-m126 deleted the docs/#1-english-document branch November 4, 2022 08:04
hayato-m126 added a commit that referenced this pull request Sep 5, 2024
Signed-off-by: Hayato Mizushima <hayato-m126@users.noreply.github.com>
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.

Add English documents
2 participants