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

Test OpenVINO export #1681

Merged
merged 2 commits into from
Feb 13, 2024
Merged

Conversation

adrianboguszewski
Copy link
Contributor

πŸ“ Description

@samet-akcay @ashwinvaidya17 is it the right place to test if all models are exportable to OpenVINO?

✨ Changes

Select what type of change your PR is:

  • 🐞 Bug fix (non-breaking change which fixes an issue)
  • πŸ”¨ Refactor (non-breaking change which refactors the code base)
  • πŸš€ New feature (non-breaking change which adds functionality)
  • πŸ’₯ Breaking change (fix or feature that would cause existing functionality to not work as expected)
  • πŸ“š Documentation update
  • πŸ”’ Security update

βœ… Checklist

Before you submit your pull request, please make sure you have completed the following steps:

  • πŸ“‹ I have summarized my changes in the CHANGELOG and followed the guidelines for my type of change (skip for minor changes, documentation updates, and test enhancements).
  • πŸ“š I have made the necessary updates to the documentation (if applicable).
  • πŸ§ͺ I have written tests that support my changes and prove that my fix is effective or my feature works (if applicable).

Copy link
Contributor

@samet-akcay samet-akcay left a comment

Choose a reason for hiding this comment

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

Thanks @adrianboguszewski. I have one suggestion to rename framework to export_type. Since framework term is not used in the main code base, the code might flow better if we stick to the export_type term that is used throughout the codebase

tests/integration/model/test_models.py Outdated Show resolved Hide resolved
tests/integration/model/test_models.py Outdated Show resolved Hide resolved
tests/integration/model/test_models.py Outdated Show resolved Hide resolved
Signed-off-by: Adrian Boguszewski <adrian.boguszewski@intel.com>
@adrianboguszewski
Copy link
Contributor Author

adrianboguszewski commented Feb 9, 2024

@samet-akcay your review has been incorporated :)

@samet-akcay samet-akcay merged commit a892215 into openvinotoolkit:main Feb 13, 2024
5 of 6 checks passed
@adrianboguszewski adrianboguszewski deleted the ov-tests branch February 14, 2024 11:35
@nguyenanhtuan1008
Copy link

nguyenanhtuan1008 commented Feb 14, 2024

@adrianboguszewski @samet-akcay
sorry, I have a question. I used command line for training: anomalib train --config <path/to/config>. Now I want to export the custom model to TORCH and OpenVINO model, how can I do it?

This my command:
anomalib train --config /workspaces/anomalib/efficient_ad.yaml --data /workspaces/anomalib/mvtec.yaml

mvtec.yaml:

class_path: anomalib.data.MVTec
init_args:
  root: /workspaces/anomalib/datasets/MVTec
  category: mvt_20240209
  image_size: [512, 512]
  center_crop: null
  normalization: imagenet
  train_batch_size: 4
  eval_batch_size: 2
  num_workers: 8
  task: SEGMENTATION
  transform_config_train: null
  transform_config_eval: null
  test_split_mode: FROM_DIR
  test_split_ratio: 0.2
  val_split_mode: SAME_AS_TEST
  val_split_ratio: 0.5
  seed: null


and efficient_ad.yaml:

model:
  class_path: anomalib.models.EfficientAd
  init_args:
    teacher_out_channels: 384
    model_size: M
    lr: 0.0001
    weight_decay: 1.0e-05
    padding: false
    pad_maps: true
    batch_size: 1

metrics:
  pixel:
    - AUROC

trainer:
  max_epochs: 1000
  max_steps: 70000

@adrianboguszewski
Copy link
Contributor Author

I believe @samet-akcay can answer this question better

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants