[shyhyawJou]

Summary

The script uses paths relative to examples/mediatek (e.g. model_export_scripts/...), so running it from the repo root fails with

Export model: mobilenetv3
python3: can't open file '/media/user/disk2/mateo/zza/executorch/model_export_scripts/mobilenet_v3.py': [Errno 2] No such file or directory

This PR updates the instructions to cd into examples/mediatek first.

Test plan

Ran the updated instructions and confirmed they work:

cd executorch/examples/mediatek
./shell_scripts/export_oss.sh mobilenetv3

Previously, running ./examples/mediatek/shell_scripts/export_oss.sh mobilenetv3 from the repo root failed because the script uses paths relative to examples/mediatek (e.g. model_export_scripts/mobilenet_v3.py).

cc @nil-is-all

[pytorch-bot]

🔗 Helpful Links

🧪 See artifacts and rendered test results at hud.pytorch.org/pr/pytorch/executorch/24142

• 📄 Preview Python docs built from this PR

Note: Links to docs will display an error until the docs builds have been completed.

⚠️ 15 Awaiting Approval

As of commit 35c20fe with merge base d07c72b ():

AWAITING APPROVAL - The following workflows need approval before CI can run:

• Build documentation (gh)
• Build Presets (gh)
• Cadence Build & Test (gh)
• Lint (gh)
• periodic (gh)
• pull (gh)
• Test ARM Backend (gh)
• Test CoreML Backend (gh)
• Test Cortex-M Backend (gh)
• Test NXP Backend (gh)
• Test QNN Backend (gh)
• Test QNN Windows MSVC build (gh)
• Test Vulkan Backend (gh)
• Test WebGPU Backend (gh)
• Test XNNPACK Backend (gh)

This comment was automatically generated by Dr. CI and updates every 15 minutes.

[meta-cla]

Hi @shyhyawJou!

Thank you for your pull request and welcome to our community.

Action Required

In order to merge any pull request (code, docs, etc.), we require contributors to sign our Contributor License Agreement, and we don't seem to have one on file for you.

Process

In order for us to review and merge your suggested changes, please sign at https://code.facebook.com/cla. If you are contributing on behalf of someone else (eg your employer), the individual CLA may not be sufficient and your employer may need to sign the corporate CLA.

Once the CLA is signed, our tooling will perform checks and validations. Afterwards, the pull request will be tagged with CLA signed. The tagging process may take up to 1 hour after signing. Please give it that time before contacting us about it.

If you have received this in error or have any questions, please contact us at cla@meta.com. Thanks!

[linux-foundation-easycla]

The committers listed above are authorized under a signed CLA.

• ✅ login: shyhyawJou / name: Shi-Yao, ZHOU (35c20fe)

[shyhyawJou]

@pytorchbot label "release notes: none"

[meta-cla]

Thank you for signing our Contributor License Agreement. We can now accept your code for this (and any) Meta Open Source project. Thanks!