#!/bin/bash lnbase=/BTagging/directory/to/be/linked for reco in p17_CC p17_MU p20_CC p20_MU; do for ntag in EqOneTag EqTwoTag; do for njet in EqFourJet EqThreeJet EqTwoJet; do for f in ${lnbase}/${reco}/$ntag/$njet/*"$njet"*.root; do fl=`basename $f` #in order to create the proper name for linked file ln -s $f ${fl%Eq*.root}${ntag}_${njet}_zero.root # ^the first part is same # effectively insert ntag and zero done done done done
https://killer.sh Pre Setup Once you've gained access to your terminal it might be wise to spend ~1 minute to setup your environment. You could set these: alias k = kubectl # will already be pre-configured export do = "--dry-run=client -o yaml" # k get pod x $do export now = "--force --grace-period 0" # k delete pod x $now Vim To make vim use 2 spaces for a tab edit ~/.vimrc to contain: set tabstop=2 set expandtab set shiftwidth=2 More setup suggestions are in the tips section . Question 1 | Contexts Task weight: 1% You have access to multiple clusters from your main terminal through kubectl contexts. Write all those context names into /opt/course/1/contexts . Next write a command to display the current context into /opt/course/1/context_default_kubectl.sh , the command should use kubectl . Finally write a second command doing the same thing into ...
Comments
Post a Comment
https://gengwg.blogspot.com/