Commit 8f3f7c5
Fix read-only numpy arrays in cross-validation (facebook#4794)
Summary:
I'm not sure why these are showing up as failures today, we migrated to Python scientific stack in july 2024, but these are deprecation warnings we should go ahead and take care of anyway. Figured would knock them out while they are causing me issues
Prompted after some failures in exports not related to my changes: https://github.com/facebook/Ax/actions/runs/21225324302/job/61070638075?fbclid=IwY2xjawPeXMFleHRuA2FlbQIxMQBicmlkETFRTkR6WlE4NHVrd3IyQXNlc3J0YwZhcHBfaWQBMAABHjTAiZi71n24w95hvzEewrKNPKOGzJisgR7t4qJ3APRMYlusgFC-gu7RLiSb_aem_Zk3pmTDonCFsJvZCTkpeMA
Add `.copy()` after `.numpy()` calls to ensure arrays are writeable.
PyTorch tensors converted via `.detach().cpu().numpy()` return read-only
arrays in some cases. The subsequent squeeze operations create read-only
views, and the in-place assignment `loo_covs[:, diag_idx, diag_idx] = loo_vars`
fails with "assignment destination is read-only" error.
Differential Revision: D911854671 parent 6045c31 commit 8f3f7c5
1 file changed
+5
-4
lines changed| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
240 | 240 | | |
241 | 241 | | |
242 | 242 | | |
243 | | - | |
244 | | - | |
| 243 | + | |
| 244 | + | |
| 245 | + | |
245 | 246 | | |
246 | 247 | | |
247 | | - | |
248 | | - | |
| 248 | + | |
| 249 | + | |
249 | 250 | | |
250 | 251 | | |
251 | 252 | | |
| |||
0 commit comments