+ Bandung gets over 300mm of rain in November, then it tapers off a bit, but shoots back up to 300+mm in March — almost like it has two peaks in its wet season.
+ In contrast, Jakarta (just ~150 km away) has a more classic single wet season, peaking around January–February.
I know elevation and geography probably play a big role here — Bandung is inland, in a valley (I think?), and surrounded by mountains, while Jakarta is coastal and low-lying. But I'm curious about the specific science behind how location and topography can split a wet season into two.
##How exactly do features like elevation, mountain barriers, and inland position shape rainfall seasonality so drastically — especially in places so close together #science
To YSK That "secure delete" doesn't work on solid state drives. In order to ensure deleted files are unrecoverable you should encrypt your disk drive.
Why YSK: "Secure delete" doesn't work on solid state drives and you should know what to do to guarantee deleted files aren't recoverable by other people.
\##Background
You may already know that when you "delete" a file, the file isn't actually erased. Instead the file still exists on your drive, instead the reference to the file in the file system's directory structure (e.g., the Master File Table in NTFS or inode table in Linux) is removed. The file still exists and it can potentially be found by examining areas of the disk that (according to the file system's directory) do not contain any current file data. In the past you could "secure delete" a file by overwriting the entire contents of the file with garbage data (random data, all zeros or all ones) sometimes several times to make sure it is no longer recoverable. However, this does not work on solid state disks. Solid state disks have a limit to how many times they can be written to, so the drive itself decides where to write data. It does this so that it can make sure that no one area of the drive is written to a lot more than others which would cause areas of the disk to become unusable while others areas are still "fresh" and can still be used. So if you tell it to overwrite a particular area of the disk there is no guarantee that data will actually be written to the physical location you specify.
\##What to do
The only way I know to guarantee that deleted files are unreadable then is to encrypt your disk. When it is encrypted no one can read any part of the disk unless they know the encryption key, so both existing files and deleted files will be unreadable without the key.
I'm working through some programing exersizes and one is to create a program which counts calories for a user and returns calories burned at specific times in minutes(10,15,20,25,30). The user burns calories at a constant rate of 3.9 cal/min:
import time as t def calorie_count(workout_time): calories_burned = CALORIES_PER_MINUTE * workout_time print("you've burned ", calories_burned, " calories in ", workout_time, " minutes!") return CALORIES_PER_MINUTE = 3.9 t.sleep(1) calorie_count(10) t.sleep(1) calorie_count(15) t.sleep(1) calorie_count(20) t.sleep(1) calorie_count(25) t.sleep(1) calorie_count(30) input("press any key to end the program")
This is what I came up with that worked. I imagined something cooler and I did all the flowcharting that I needed to complete with a few functions, problem is I don't know enough about the date time module or time in python to actually implement what I "engineered":
The issue I had was I couldn't just subtract "now" from my "start time" to get an "amount of minutes passed since the start". What I wanted to do was create a case/switch function which would run my "calorie\_count" function at the specified intervals and print calories burned. I'm pretty sure I've seen it done in some books(I'm reading PACKT's Learn Python Programming) but can't find it currently and the Python datetime documentation isn't easy.to ttp://easy.to understand for a beginner So, my question is, \#how do I subtract time and get a integer I can use #dev #programming #technology oaw() source