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

Add Anomaly alias #3832

Conversation

ashwinvaidya17
Copy link
Contributor

Summary

  • As requested in CVS-147611

How to test

Checklist

  • I have added unit tests to cover my changes.​
  • I have added integration tests to cover my changes.​
  • I have ran e2e tests and there is no issues.
  • I have added the description of my changes into CHANGELOG in my target branch (e.g., CHANGELOG in develop).​
  • I have updated the documentation in my target branch accordingly (e.g., documentation in develop).
  • I have linked related issues.

License

  • I submit my code changes under the same Apache License that covers the project.
    Feel free to contact the maintainers if that's a concern.
  • I have updated the license header for each file (see an example below).
# Copyright (C) 2024 Intel Corporation
# SPDX-License-Identifier: Apache-2.0

GalyaZalesskaya and others added 30 commits November 9, 2023 10:39
)

* Fix h-label bug of missing parent labels in output

* Fix h-label test data label schema

* Update CHANGELOG.md

---------
Signed-off-by: Songki Choi <songki.choi@intel.com>
update publish workflow to push whl to internal pypi
Signed-off-by: Songki Choi <songki.choi@intel.com>
Signed-off-by: Songki Choi <songki.choi@intel.com>
…k/1.4.4-to-1.5.0

Mergeback 1.4.4 to releases/1.5.0
* update release note and readme

* remove package upload step on internal publish wf
* Update publish workflow for tag checking (openvinotoolkit#2632)

* Update e2e tests for XAI Detection (openvinotoolkit#2634)

* Disable QAT for newly added models (openvinotoolkit#2636)

* Update release note and readme (openvinotoolkit#2637)

* remove package upload step on internal publish wf

* update release note and, changelog, and readme

* update version string to 1.6.0dev

---------

Co-authored-by: Galina Zalesskaya <galina.zalesskaya@intel.com>
Co-authored-by: Jaeguk Hyun <jaeguk.hyun@intel.com>
@ashwinvaidya17
Copy link
Contributor Author

ashwinvaidya17 commented Aug 21, 2024

tox -e pre-commit-all-py310-pt1: This command reproduces exactly the same as CI: I pushed the change to the appropriate branch. ccba2e7 c261717

so now, let's see test

Thanks for pushing the change. This is what I had tried based on the actions file.

conda create -n temp python=3.10 -y
conda activate temp
pip install --require-hashes --no-deps -r requirements/gh-actions.txt
pip-compile --generate-hashes -o /tmp/otx-dev-requirements.txt requirements/dev.txt
pip install --require-hashes --no-deps -r /tmp/otx-dev-requirements.txt
rm /tmp/otx-dev-requirements.txt
tox -vv -e pre-commit-all-py310-pt1

But even with this I got the same result.

Signed-off-by: Ashwin Vaidya <ashwinnitinvaidya@gmail.com>
…shwinvaidya17/training_extensions into ashwin/anomaly_geti_task_migration_1_6
@ashwinvaidya17 ashwinvaidya17 mentioned this pull request Aug 21, 2024
8 tasks
Signed-off-by: Ashwin Vaidya <ashwinnitinvaidya@gmail.com>
@chuneuny-emily
Copy link
Contributor

@ashwinvaidya17 - OTX1.6.4 was already released into Geti 2.3.0 and develop branches. What is the Geti target version for this PR ?

@ashwinvaidya17
Copy link
Contributor Author

@ashwinvaidya17 - OTX1.6.4 was already released into Geti 2.3.0 and develop branches. What is the Geti target version for this PR ?

I am assuming the next version then. Maybe @A-Artemis can say more about this.

@A-Artemis
Copy link
Contributor

@ashwinvaidya17 - OTX1.6.4 was already released into Geti 2.3.0 and develop branches. What is the Geti target version for this PR ?

The Geti target is 2.5.0.

@chuneuny-emily
Copy link
Contributor

@A-Artemis @ashwinvaidya17 - It is difficult to merge the code changes targeting Geti 2.5 into the official OTX1.6.5 aimed at integrating Geti 2.3/2.4. For Geti 2.5, OTX2.x integration is scheduled. If an early drop is required due to preliminary work by other teams, it seems necessary to create a separate branch to check updated features. What do you think?

@chuneuny-emily
Copy link
Contributor

@ashwinvaidya17 - Please target this PR to OTX develop branch.
@A-Artemis - Please create a your own branch from Geti develop, then I'll integrate the latest OTX develop into the branch for your work.

@ashwinvaidya17
Copy link
Contributor Author

@chuneuny-emily This pr #3818 targets develop branch

@samet-akcay
Copy link
Contributor

As suggested by @chuneuny-emily, this is not needed and can be closed.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
ALGO Any changes in OTX Algo Tasks implementation API Any changes in OTX API CLI Any changes in OTE CLI TEST Any changes in tests
Projects
None yet
Development

Successfully merging this pull request may close these issues.