Given
echo %CD%
result: E:\abcd\efg\hijk\lmno
To pull out "E:\abcd\efg" from this path and set it to a variable named TRUNK:
for /f "tokens=1,2,3 delims=\" %%G in ("%CD%") do set TRUNK=%%G\%%H\%%I
echo %TRUNK%
result: E:\abcd\efg
Note the need to restore the backslashes that were pulled out as token delimiters.
If you prefer to convert the path to use forward slashes while you're at it:
for /f "tokens=1,2,3 delims=\" %%G in ("%CD%") do set TRUNK=%%G/%%H/%%I
echo %TRUNK%
I had been creating a time stamp just to give my output unique file names so as not to overwrite previous test output.
I'd been doing this:
REM TT= time tag for this runset T=%time%set TT=%T:~0,2%%T:~3,2%%T:~6,2%
It works fine after 10 am:
C:\Users\mharrison>set TT=%T:~0,2%%T:~3,2%%T:~6,2%C:\Users\mharrison>echo %TT%100359C:\Users\mharrison>echo filename%TT%filename100359
I've been using this time stamp method for weeks, but apparently never before 10 am. It broke my code this morning. Before 10am, the plain old time inserts a space:
C:\Users\mharrison>echo %time%9:56:08.38
So when I try to append it to make a unique file name, I insert a space in the file name, which confuses the code:
C:\Users\mharrison>set TT=%T:~0,2%%T:~3,2%%T:~6,2%C:\Users\mharrison>echo %TT%95740C:\Users\mharrison>echo filename%TT%filename 95740
So I changed the method to only use the 2nd digit of the hour:
REM TT= time tag for this runset T=%time%set TT=%T:~1,1%%T:~3,2%%T:~6,2%
C:\Users\mharrison>set T=%time%
C:\Users\mharrison>echo %T%10:11:54.96
C:\Users\mharrison>set TT=%T:~1,1%%T:~3,2%%T:~6,2%%T:~1,1%%T:~3,2%%T:~6,2%C:\Users\mharrison>echo %TT%0115401154C:\Users\mharrison>echo filename%TT%filename0115401154
from java (oracle.com) and java (oracle.com):
Sets the minimum and the initial size (in bytes) of the heap. This value must be a multiple of 1024 and greater than 1 MB. Append the letter k or K to indicate kilobytes, m or M to indicate megabytes, g or G to indicate gigabytes.
The following examples show how to set the size of allocated memory to 6 MB using various units:
-Xms6291456 -Xms6144k -Xms6m
Specifies the maximum size (in bytes) of the memory allocation pool in bytes. This value must be a multiple of 1024 and greater than 2 MB. Append the letter k or K to indicate kilobytes, m or M to indicate megabytes, g or G to indicate gigabytes. The default value is chosen at runtime based on system configuration. For server deployments, -Xms and -Xmx are often set to the same value. See the section "Ergonomics" in Java SE HotSpot Virtual Machine Garbage Collection Tuning Guide at http://docs.oracle.com/javase/8/docs/technotes/guides/vm/gctuning/index.html.
The following examples show how to set the maximum allowed size of allocated memory to 80 MB using various units:
-Xmx83886080 -Xmx81920k -Xmx80m
The -Xmx option is equivalent to -XX:MaxHeapSize.
I compressed my PC's Windows 10 C drive after spending a very long time trying to figure out how to get it out of the "red". Unfortunately, the next time I started up LTS Ubuntu, it complained about the virtual disk being compressed and would not start up.
I followed other web advice to look under C:\users\[me]\AppData\Local\Packages
There I found something named CanonicalGroupLimited.Ubuntu20.04onWindows_79rblahblah ..
After I decompressed that package LTS Ubuntu worked again.
From a colleague:
In case you ever have to do an f.seek():
When calculating record offsets, python only does a consistent
and correct len() value if your file is opened in binary.
We often copy a few fake records to create a large input file with which to test how the code handles it.
It's a useful test; but don't use it to gauge performance.
Data from repeated records can be cached and reused. If your production data will vary, then it won't get the same use out of caching. Caching could even hurt performance.
More complex solutions at https://stackoverflow.com/questions/28700043/thousands-separator-of-an-integer-value
-->C:\Users\mharrison>echo %CD%
C:\Users\mharrison
C:\Users\mharrison>dir %CD%\..\..
Volume in drive C is Windows
Volume Serial Number is E431-FA9F
Directory of C:\
03/03/2017 11:02 AM <DIR> DRIVERS
04/11/2018 07:38 PM <DIR> PerfLogs
05/31/2019 02:25 PM <DIR> Program Files
05/15/2019 09:04 AM <DIR> Program Files (x86)
03/25/2019 05:33 PM <DIR> test
05/13/2019 10:56 AM <DIR> Tools
04/09/2019 09:21 AM <DIR> Users
08/08/2019 06:02 PM <DIR> Windows
0 File(s) 0 bytes
8 Dir(s) 61,991,501,824 bytes free
C:\Users\mharrison>dir %CD%/..
Invalid switch - "..".
yum -y install firstboot
chkconfig firstboot on
yum -y update kernel panic not able to mount root fs on unknown block(0,0) 
rem Test Timing
rem You might need to set this in later versions and also use !time setlocal enabledelayedexpansion
set start_time=%time%
echo start_time is %start_time%
pause
rem Replace above 'pause' with activity to be timed (approx).
set end_time=%time%
rem Now calculate time difference
echo started %start_time%
echo ended %end_time%
rem To get a substring, do this:
rem %variable:~num_chars_to_skip,num_chars_to_keep%
rem Here we also prepend "1" to 2-digits and then subtract 100
rem to avoid numbers like "02"
rem which can cause errors in the windows batch interpreter.
set sh=1%start_time:~0,2%
set eh=1%end_time:~0,2%
set sm=1%start_time:~3,2%
set em=1%end_time:~3,2%
set ss=1%start_time:~6,2%
set es=1%end_time:~6,2%
set sms=1%start_time:~9,2%
set ems=1%end_time:~9,2%
echo sh %sh%, eh %eh%, sm %sm%, em %em% and sms %sms%, ems %ems%
pause
set /A start_secs=(%sh%-100)*3600 + (%sm%-100)*60 + (%ss%-100)
set /A end_secs=(%eh%-100)*3600 + (%em%-100)*60 + (%es% - 100)
set /A start_ms=(%start_secs%)*100 + (%sms% - 100)
set /A end_ms=(%end_secs%)*100 + (%ems% - 100)
set /A diff=%end_ms% - %start_ms%
echo %start_ms% to %end_ms% is %diff% milliseconds pause
# if no input number, assume i=1# general methoddef stitch(stitch_name,int i=1): crochet i stitch_name stitches
def chain(int i=1): stitch(chain,i)
def dc(int i=1): stitch(double-crochet, i)def sc(int i=1): stitch(single-crochet, i)
def skip(i): skip i stitches from previous row before the next stitch in this row
#The definition of "shell" varies with pattern. In this pattern:
def shell(int i, stitch previous_row_stitch):
dc(i) into the same previous_row_stitch
def flip_work():
#Rows are worked away from the direction of the dominant hand,
#If you're right-handed, this means: from right to left
#Turning chains are chains made at the end of the row.
def dc_turning_chain(int i=3):
chain(i)
flip_work()
Once I have seen the request I generally do one of 4 things with it almost immediately.
1. If I know that this is a duplicate of another request I close the new one and mark it as a duplicate of the original.
2. If I see no value to the request, or I see value but the opportunity cost is too high, then I will just close it.
3. If I see value to the request, and it fits in with much of the feedback received on all of the other channels then I will assign it to be considered for a release
4. Finally I can choose to do nothing with it right now. This final one allows me to bear it in mind and use it for consideration on future requests.
From http://johnpeltier.com/blog/2013/12/12/feature-requests/:
- You need to know what the goals or key business drivers are for your product so you can create a scorecard that includes these key metrics.;
- If it is not clear who owns prioritization, your scoring will not be trusted. It's essential to know who is in charge;
- If there is not enough detail per feature, then the functionality of each feature will be unclear.
From https://www.quora.com/How-should-a-product-manager-handle-communication-to-internal-people-who-make-feature-requests-when-the-volume-of-requests-far-exceeds-engineering-capacity:Once prioritized, you’ll want to communicate your plans in a roadmap that doesn’t tie you to specific dates.
- Ideas that don’t fit with the long term vision for the product at all. These receive a polite rejection.
- Many, many good ideas that you might do someday. These are usually acknowledged but sit in the “someday” bucket.
- A few ideas which map to the area of the product that needs work next, or the next most important problem to solve.
The backlog should not be a dumping ground for all ideas that may get worked on eventually, or may not. It will become impossible to manage and just gives the requestor a false sense of security by having it added. If you don't see yourself working on a backlog item in the next ~4 months, I recommend just telling the person no, point blank, or maintaining a separate list or roadmap outside of the backlog for these items.
python scriptname.py A 1 C 3 B 2
dd={}for i in range(1,len(argv),2): dd[sys.argv[i]]=sys.argv[i+1] >>> params=['scriptname','A',1,'C',3,'B',2]
>>> dd={}
>>> for i in range(1,len(params),2):
... dd[params[i]]=params[i+1]
...
>>> dd
{'A': 1, 'C': 3, 'B': 2}
>>> default_dd={'A':1,'B':2,'C':3,'D':4,'E':5}
>>> dd={'B':2000,'D':4000}
>>> for key in default_dd.keys():
... if not key in dd.keys():
... dd[key]=default_dd[key]
...
>>> dd
{'A': 1, 'C': 3, 'B': 2000, 'E': 5, 'D': 4000}
if __name__ == "__main__": #initialize list of expected parameters, in order dd_parameters=['scriptname','A','B','C','D','E'] dd={} if len(sys.argv) > 1: #loop through the actual input parameters for i in range(1, len(sys.argv)): dd[dd_parameters[i]]=sys.argv[i] >>> std_parms=['scriptname','A','B','C','D'] >>> input_parms=['scriptname','A_Value','B_Value'] >>> dd={} >>> for i in range(1,len(input_parms)): ... dd[std_parms[i]]=input_parms[i] ... >>> dd {'A': 'A_Value', 'B': 'B_Value'}
