Backward compatibility of ptl with live.spec on iOS
See original GitHub issueVersion
0.2.0
Problem Area
react-native-pytorch-core (core package)
Steps to Reproduce
- make ptl file with live.spec.json
- build a project with ptl on iOS
- inference a input image
- get this error
code: EUNSPECIFIED,
domain: react_native_pytorch_core.BaseIValuePackerError,
message: decodeObjectsError,
name: Error,
nativeStackIOS: [Array],
stack:
Error: decodeObjectsError
the project works well in 0.1.3, but the error comes up after upgrade to 0.2.0. Is there no backward compatibility for ptl with live.spec?
No problem on Android.
Expected Results
No error
Code example, screenshot, or link to repository
No response
Issue Analytics
- State:
- Created a year ago
- Comments:7 (4 by maintainers)
Top Results From Across the Web
Swift UI backward compatibility | Apple Developer Forums
I am new to SwiftUI and thinking of converting my UIKit app. My deployment target is the last version of iOS 13. If...
Read more >Backward Compatibility - Ableton
Any set made in an earlier version of Live can be opened in any later versions of Live. For example, a set made...
Read more >Xbox Backward Compatible Games
Discover the library of Xbox backward compatible games. Experience game franchises from past generations and enjoy the games you love at no additional...
Read more >Swift's new concurrency system gains backward compatibility ...
Starting in Xcode 13.2, Swift's new suite of concurrency features are now backward compatible all the way back to iOS 13, macOS Catalina, ......
Read more >iOS 16 Supported Devices: Which iPhones are compatible?
The older ones lacked the artificial intelligence power to handle things like Live Text in Photos and on-device speech processing for Siri.
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
@raedle , thanks for resolving the issue! I’ve verified that your fix works fine.
I will try to upgrade to the new PlayTorch SDK JavaScript API by referring to your explanation and let you know if I get stuck.
Thank you always!
@SomaKishimoto, we found the culprit. After upgrading the LibTorch-Lite library from version
1.10.0
to1.12.0
, the kind support changed toc10::DynamicType
. Unfortunately, the unit tests didn’t catch this. We have a fix in #99. When we merged the change, it will be available in thereact-native-pytorch-core@nightly
or the next planned release0.2.1
.Alternatively, as mentioned, it might be worth upgrading to the new PlayTorch SDK JavaScript API. The
useObjectDetection.ts
in the repo should be compatible with your model’s interface (according to the live spec).You’d have to change the
mean
andstd
for thenormalize
function in thepackFn
(see code).The
scaleWidth
andscaleHeight
can be set in theresize
function in thepackFn
(see code)In the
unpackFn
, use theprobabilityThreshold
and resolve the classes (see code)Let me know if you have question or need advice!