technical:recipes:keras-in-virtualenv

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Next revision
Previous revision
Next revisionBoth sides next revision
technical:recipes:keras-in-virtualenv [2020-02-04 12:22] – created freytechnical:recipes:keras-in-virtualenv [2020-02-04 12:25] – [Create Keras Virtualenv] frey
Line 38: Line 38:
  
 <code bash> <code bash>
-(root) [(it_nss:frey)@login01 keras]$ conda create --prefix=${WORKDIR}/sw/keras/20200204-sklearn keras numpy pip+(root) [(it_nss:frey)@login01 ~]$ conda create --prefix=${WORKDIR}/sw/keras/20200204-sklearn keras numpy pip
 </code> </code>
  
Line 47: Line 47:
 </code> </code>
  
-Answer "y" to create the virtualenv.  If successful, text will be displayed that mentions source'ing a file to activate the virtualenv:  refrain from doing that, and instead use VALET to manage the Keras virtualenv instances.+Answer "y" to create the virtualenv.  If successful, text will be displayed that mentions source'ing a file to activate the virtualenv:  refrain from doing that, and instead use VALET to manage the Keras virtualenv instances.  Rollback the ''intel-python'' environment changes before proceeding:
  
 +<code bash>
 +(root) [(it_nss:frey)@login01 ~]$ vpkg_rollback
 +[(it_nss:frey)@login01 ~]$ 
 +</code>
 +
 +Notice the ''(root)'' has disappeared from the prompt, indicating that the baseline virtualenv has been deactivated.
 ===== VALET Package Definition ===== ===== VALET Package Definition =====
  
Line 70: Line 76:
 </file> </file>
  
-would be added to ''${WORKDIR}/sw/valet/keras.vpkg_yaml'' If the file already exists, add your new version at the same level as others:+would be added to ''${WORKDIR}/sw/valet/keras.vpkg_yaml'' If that file already exists, add your new version at the same level as others:
  
 <file keras.vpkg_yaml> <file keras.vpkg_yaml>
Line 97: Line 103:
 </file> </file>
  
-<note tip>On Caviness, VALET consults ''${WORKDIR}/sw/valet'' by default after the user has used the ''workgroup'' command.</note>+<note tip>On Caviness after a user has used the ''workgroup'' command, VALET searches for package definitions in ''${WORKDIR}/sw/valet'' by default.</note> 
 + 
  • technical/recipes/keras-in-virtualenv.txt
  • Last modified: 2021-08-06 13:00
  • by frey