Open JRowswell opened 2 months ago
Still unable to test
Is it possible the init_env hasn't been shipped with the bundled file?
Help would be appreciated.
Cheers
Would you like to give v0.4.5 a try? It is in active development and should not need anything special for centralized installation, just to place a folder into a python hooks path should be enough.
On Wed, May 22, 2024 at 2:53 AM JRowswell @.***> wrote:
Still unable to test
Is it possible the init_env hasn't been shipped with the bundled file?
Help would be appreciated.
Cheers
— Reply to this email directly, view it on GitHub https://github.com/talosh/flameTimewarpML/issues/93#issuecomment-2123728445, or unsubscribe https://github.com/notifications/unsubscribe-auth/AMBGYKDJZAQ4HQADLWHGKJDZDP3BHAVCNFSM6AAAAABHTZTO2OVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCMRTG4ZDQNBUGU . You are receiving this because you are subscribed to this thread.Message ID: @.***>
Sounds good!
Cheers
Does this mean it won't ask to unpack each time a new user opens flame?
Cheers
Yes there’s no packed python environment, it just lives in packages folder and avalable straight away.Sent from my iPhoneOn 30 May 2024, at 08:20, JRowswell @.***> wrote: Does this mean when I install it on more than one machine it won't ask to unpack each time? Cheers
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you commented.Message ID: @.***>
There is v0.4.5 dev 003 in releases to test, would you mind to provide any feedback on if it is works for you as a centralized install for many machines?
Hey,
Probably just my lack of knowledge/misreading but I can't seem to run this command in the central install instructions: /mnt/software/flameTimewarpML/init_env /mnt/software/miniconda3/ # Linux
I get this error: -bash: /mnt/software/flameTimewarpML/init_env: No such file or directory
I've run through all the instructions successfully so far (no errors) so not sure what I am doing wrong. Any help would be greatly appreciated!
Cheers