Update v1.py

[valentina-faraco]

Multi-Slicer window

Description

Please include a summary of the change and which issue is fixed or implemented. Please also include relevant motivation and context (e.g. links, docs, tickets etc.).

List any dependencies that are required for this change.

Type of change

Please delete options that are not relevant.

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• This change requires a documentation update

How has this change been tested, please provide a testcase or example of how you tested the change?

YOUR_ANSWER

Any specific deployment considerations

For example, documentation changes, usability, usage/costs, secrets, etc.

Docs

• Docs updated? What were the changes:

[CLAassistant]

All committers have signed the CLA.

[PawelPeczek-Roboflow]

Hello there :)
Thanks for contribution - could you elaborate more on the type of change you want to introduce?

[valentina-faraco]

Hi, I would like to introduce the possibility of applying multiple slicers of different sizes in order to obtain a more accurate detection for smaller and larger elements within the given input image. Thanks, Valentina Valentina Faraco AI Software Engineer ***@***.******@***.***> +39 3346876153 [cid:ae0a2b13-ad22-405b-b6ca-a69024b6c855] WWW.LUTECH.GROUP<https://lutech.group/> Lutech SpA • Via Orfeo Mazzitelli, 258/e 70124, Bari (BA), Italia P.IVA 02824320176 – Milano – REA-MI 1666842

…

________________________________ Da: Paweł Pęczek ***@***.***> Inviato: martedì 12 novembre 2024 11:15 A: roboflow/inference ***@***.***> Cc: Valentina Faraco ***@***.***>; Author ***@***.***> Oggetto: [EXT] Re: [roboflow/inference] Update v1.py (PR #796) Non ricevi spesso messaggi di posta elettronica da ***@***.*** Scopri perché è importante<https://aka.ms/LearnAboutSenderIdentification> Hello there :) Thanks for contribution - could you elaborate more on the type of change you want to introduce? — Reply to this email directly, view it on GitHub<#796 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/BM3UWP27H4XCVBNJVDMT4ID2AHIL5AVCNFSM6AAAAABRTUMWBKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDINZQGEZDQMRQGI>. You are receiving this because you authored the thread.Message ID: ***@***.***>

______________________________________________________________________________________________________________________________________________________________ Il contenuto di questo messaggio e-mail e di ogni eventuale allegato è strettamente confidenziale e indirizzato esclusivamente al destinatario indicato. Tutte le informazioni contenute sono soggette ad obbligo di riservatezza ai sensi del Regolamento UE 2016/679 GDPR e del D.Lgs 196/2003 e sm. Il trattamento non autorizzato del contenuto trasmesso e/o allegato dal mittente è vietato. In caso di erronea ricezione il destinatario è pregato di contattare immediatamente il mittente e cancellare al più presto il messaggio. Grazie. The contents and any attachments of this e-mail are strictly confidential and addressed exclusively to the designated addressee. Any information in this e-mail is subject to an obligation of confidentiality in accordance with EU regulation 2016/679 and D.Lgs. 196/2003. Unauthorized treatment of the content and/or any attachments of this e-mail is forbidden. In the event of incorrect reception the recipient must immediately contact the sender and delete as soon as possible the e-mail. Thank you. Lutech Spa – P.IVA 02824320176 – Milano – REA-MI 1666842

[PawelPeczek-Roboflow]

ok, that's a valid idea but I cannot approve the change in a form as is - I believe it may not work (change of the run(...) method without altering manifest) and that's also a breaking change for the slicer block

[valentina-faraco]

How can this part be integrated? Valentina Faraco AI Software Engineer ***@***.******@***.***> +39 3346876153 [cid:2b95226e-a30e-41f1-b10c-87af8497d2ea] WWW.LUTECH.GROUP<https://lutech.group/> Lutech SpA • Via Orfeo Mazzitelli, 258/e 70124, Bari (BA), Italia P.IVA 02824320176 – Milano – REA-MI 1666842

…

________________________________ Da: Paweł Pęczek ***@***.***> Inviato: martedì 12 novembre 2024 11:26 A: roboflow/inference ***@***.***> Cc: Valentina Faraco ***@***.***>; Author ***@***.***> Oggetto: [EXT] Re: [roboflow/inference] Update v1.py (PR #796) Non ricevi spesso messaggi di posta elettronica da ***@***.*** Scopri perché è importante<https://aka.ms/LearnAboutSenderIdentification> ok, that's a valid idea but I cannot approve the change in a form as is - I believe it may not work (change of the run(...) method without altering manifest) and that's also a breaking change for the slicer block — Reply to this email directly, view it on GitHub<#796 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/BM3UWP23BCS7ENC7XCGG6CL2AHJW5AVCNFSM6AAAAABRTUMWBKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDINZQGE2TGOBUGY>. You are receiving this because you authored the thread.Message ID: ***@***.***>

______________________________________________________________________________________________________________________________________________________________ Il contenuto di questo messaggio e-mail e di ogni eventuale allegato è strettamente confidenziale e indirizzato esclusivamente al destinatario indicato. Tutte le informazioni contenute sono soggette ad obbligo di riservatezza ai sensi del Regolamento UE 2016/679 GDPR e del D.Lgs 196/2003 e sm. Il trattamento non autorizzato del contenuto trasmesso e/o allegato dal mittente è vietato. In caso di erronea ricezione il destinatario è pregato di contattare immediatamente il mittente e cancellare al più presto il messaggio. Grazie. The contents and any attachments of this e-mail are strictly confidential and addressed exclusively to the designated addressee. Any information in this e-mail is subject to an obligation of confidentiality in accordance with EU regulation 2016/679 and D.Lgs. 196/2003. Unauthorized treatment of the content and/or any attachments of this e-mail is forbidden. In the event of incorrect reception the recipient must immediately contact the sender and delete as soon as possible the e-mail. Thank you. Lutech Spa – P.IVA 02824320176 – Milano – REA-MI 1666842

[PawelPeczek-Roboflow]

I believe the proper way is to create the block in version v2, yet I do not have an idea on how to easily pass the arguments such that it is clear for all users - including the one utilising Roboflow UI - especially that we would need to resign from simple params of meaningful names in favour of less verbose inputs - as lists of specs seems to be the only natural way of providing params in the scenario you outlined.

My hunch now is to have a mode parameter with the default being old behaviour and inputs should be interpreted w.r.t. the value of mode

[yeldarby]

Another option is subclassing this block to get the behavior you want in a new block and using it as a custom block in your server.