As we discussed, when we produce difference hdf files on our personal computers, we would like to be able to give the path in the .cami file and read these files by pyzebra, as is already working for .ccl and dat files.
The solution to write these files at our afs accounts works works, but needs the extra step in data manipulation.
*Created by: zaharko*
As we discussed, when we produce difference hdf files on our personal computers, we would like to be able to give the path in the .cami file and read these files by pyzebra, as is already working for .ccl and dat files.
The solution to write these files at our afs accounts works works, but needs the extra step in data manipulation.
It is possible to read local files on personal computers via their paths, e.g. if they are in .cami files. The only possibility is it upload hdf5 files directly, similar how it's done for .ccl and .dat files. So, the only difference is that there will be no option to change parameters as it's done via cami. Would it work for you this way?
*Created by: ivan-usov*
It is possible to read local files on personal computers via their paths, e.g. if they are in .cami files. The only possibility is it upload hdf5 files directly, similar how it's done for .ccl and .dat files. So, the only difference is that there will be no option to change parameters as it's done via cami. Would it work for you this way?
It is possible to read local files on personal computers via their paths, e.g. if they are in .cami files. The only possibility is it upload hdf5 files directly, similar how it's done for .ccl and .dat files. So, the only difference is that there will be no option to change parameters as it's done via cami. Would it work for you this way?
*Created by: zaharko*
No really
On 5 Oct 2021, at 16:18, Ivan Usov ***@***.******@***.***>> wrote:
It is possible to read local files on personal computers via their paths, e.g. if they are in .cami files. The only possibility is it upload hdf5 files directly, similar how it's done for .ccl and .dat files. So, the only difference is that there will be no option to change parameters as it's done via cami. Would it work for you this way?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub<https://github.com/paulscherrerinstitute/pyzebra/issues/38#issuecomment-934456520>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AMBMFVB3JUVKYGKQGDEV7KLUFMCLZANCNFSM5DLVY7PA>.
Triage notifications on the go with GitHub Mobile for iOS<https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675> or Android<https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>.
[ { ***@***.***": "http://schema.org", ***@***.***": "EmailMessage", "potentialAction": { ***@***.***": "ViewAction", "target": "https://github.com/paulscherrerinstitute/pyzebra/issues/38#issuecomment-934456520", "url": "https://github.com/paulscherrerinstitute/pyzebra/issues/38#issuecomment-934456520", "name": "View Issue" }, "description": "View this Issue on GitHub", "publisher": { ***@***.***": "Organization", "name": "GitHub", "url": "https://github.com" } } ]
It is not possible to read local files on personal computers via their paths ...
In other words, paths in cami files must be visible for the pyzebra server located at PSI.
*Created by: ivan-usov*
I noticed a typo in my previous post.
> It is **not** possible to read local files on personal computers via their paths ...
In other words, paths in cami files must be visible for the pyzebra server located at PSI.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Created by: zaharko
As we discussed, when we produce difference hdf files on our personal computers, we would like to be able to give the path in the .cami file and read these files by pyzebra, as is already working for .ccl and dat files.
The solution to write these files at our afs accounts works works, but needs the extra step in data manipulation.
Created by: ivan-usov
It is possible to read local files on personal computers via their paths, e.g. if they are in .cami files. The only possibility is it upload hdf5 files directly, similar how it's done for .ccl and .dat files. So, the only difference is that there will be no option to change parameters as it's done via cami. Would it work for you this way?
Created by: zaharko
No really
On 5 Oct 2021, at 16:18, Ivan Usov @.@.>> wrote:
It is possible to read local files on personal computers via their paths, e.g. if they are in .cami files. The only possibility is it upload hdf5 files directly, similar how it's done for .ccl and .dat files. So, the only difference is that there will be no option to change parameters as it's done via cami. Would it work for you this way?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHubhttps://github.com/paulscherrerinstitute/pyzebra/issues/38#issuecomment-934456520, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AMBMFVB3JUVKYGKQGDEV7KLUFMCLZANCNFSM5DLVY7PA.
Triage notifications on the go with GitHub Mobile for iOShttps://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Androidhttps://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.
[ { @.": "http://schema.org", @.": "EmailMessage", "potentialAction": { @.": "ViewAction", "target": "https://github.com/paulscherrerinstitute/pyzebra/issues/38#issuecomment-934456520", "url": "https://github.com/paulscherrerinstitute/pyzebra/issues/38#issuecomment-934456520", "name": "View Issue" }, "description": "View this Issue on GitHub", "publisher": { @.": "Organization", "name": "GitHub", "url": "https://github.com" } } ]
Created by: ivan-usov
I noticed a typo in my previous post.
In other words, paths in cami files must be visible for the pyzebra server located at PSI.
Created by: ivan-usov
The change is on the test server. Now one could upload an hdf5 file directly via a widget under "or upload .hdf file" text.