MonDie

Thank you! If you'll be doing security, you could try SELinux. It was developed by the NSA, albeit in 1998, and was considered more secure at the time. However Ubuntu has increased its security with AppArmor since then, so I don't know which is preferable. Unless there's a separate iso image, you might have to install the old Karmic Koala edition of Ubuntu, then download and install the meta-package. https://wiki.ubuntu.com/SELinux

I found a trinomial distribution formula that's much the same to the binomial formula, but I'm not 100% sure that it's ordering the events by degree of success. I want to have strong successes and weak successes. https://onlinecourses.science.psu.edu/stat414/node/106 Where the event types are A, B, and C, and lowercase denotes each's number of occurences, their formula goes like this. [math]\frac{(a+b+c)!}{a! b! c!} P(A)^{a} P(B)^{b} P©^{c}[/math] which is basically just an expanded version of the binomial formula which can be written as [math]\frac{(a+b)!}{a! b!} P(A)^{a} P(B)^{b}[/math] The question is, could I write it so that each A (strong success) also counts as a B (strong or weak success)?

What kinds of employers?

Not to mention, you can stop taking a drug and it gradually leaves your system. I'm guessing they'll give you the gene's product in drug form first, so you test it out before making that commitment.

They call it gene therapy. The genes are delivered by innocuous viruses. But how much can change an already developed organism?

Most of the echoes are only there for debugging, and will be removed in the final. The code you provide is incomprehensible to me—I skipped learning awk because it looked complicated—, but I took some of your advice and made my own simplified script. #! /bin/bash list="" for i in $(cat ~/astr/dates); do ## Assigns the next line of dates to $date via the i variable. date=$(echo $i | tr "z" " ") echo "date "$date ## Greps the table with $date, then isolates and assigns the longitude value(s). longitude=$(cat ~/astr/merc | grep "$date" | awk '{print $3}') ## Appends $longitude to $list. list=$list" "$longitude echo $list done ## Indicate completion of the until loop. echo "List completed." or, without the comments and excessive echoes, #! /bin/bash list="" for i in $(cat ~/astr/dates); do date=$(echo $i | tr "z" " ") longitude=$(cat ~/astr/merc | grep "$date" | awk '{print $3}') list=$list" "$longitude done Apparently the for loop runs line-by-line down the output of a command, in this case cat ~/astr/dates, assigning each successive line to $i. That was very convenient. I didn't even have to translate the whitespace back into new lines. It was however interpretting whitespace as it does new lines, so you have to replace whitespace with a "z" in the dates file.

I edited to add about Lubuntu, which is often run on old pieces of junk like you find at garage sales. https://wiki.ubuntu.com/Lubuntu

If it's Ubuntu, it will ask you during installation, but I would back up your files to be safe. Or run Lubuntu on any old piece of junk you can find at a garage sale. https://wiki.ubuntu.com/Lubuntu All linux distributions use mostly the same command line utilities. I recommend starting with Ubuntu. Just remember that the GUIs are just frontends, and you can often do more with the command line utilities. So don't be lazy! Don't learn GParted, learn fdisk. Don't use GUFW, but learn ufw and eventually iptables. Don't use Software Center, but learn apt-get. The deeper you dig, the more similar the different Linux distributions are to eachother. Most importantly, read the info and man pages! Just type info/man name-of-utility ubuntu.com is an invaluable resource.

I'm testing my past self's claim that I could, without peeking, identify the days when Venus or Mars was contacting my natal chart. I am however creating a more flexible and 100% free program that can test an array of similar claims. The user generates the ephemeris from nasa.gov and thus can choose any celestial body, and they define what longitude ranges count as successes or failures in their binomial probability distributions.

It's more than just an infinite loop. It's going through every single line of the ephemeris obtained from the NASA site (~/astr/merc), but it should only go through those lines that match the dates in ~/astr/dates. I made an altered script for debugging. It prints the variable name before each variable so we can identify them, and it has a read random before done to halt the script before each loop. Apparently it assigns nothing to longitude on the first round, and nothing to longitude or dlist on the second round. On the third round, dlist is empty—which doesn't terminate the until loop for some reason—, so nothing gets assigned to date. Because $date is empty, grep selects the entire ephemeris, and the program assigns all the longitudes to $longitude at once, and the program repeatedly appends this to $list. #! /bin/bash dlist=$(cat ~/astr/dates) echo "initial dlist "$dlist list="" until [[ dlist == "" ]]; do ## Assigns the next value in $dlist to $date, then removes it from $dlist. date=$(echo $dlist | sed "s/-/z/" | tr "_" "\n" | grep z | sed "s/z/-/") echo "date "$date dlist=$(echo $dlist | sed "s/-/z/" | tr "_" "\n" | grep -v z) echo "dlist "$dlist ## Greps the table with $date, then isolates and assigns the longitude value(s). longitude=$(cat ~/astr/merc | grep "$date" | sed "s/\./\,/" | tr " " "\n" | grep [,] | tr "," ".") echo "longitude "$longitude ## Appends $longitude to $list. list=$list" "$longitude read random done ## Indicate completion of the until loop. echo "List completed." I've spotted it! The problem with longitude was a faulty dates file. I entered Jan-1 instead of Jan-01, which appears nowhere in the ephemeris. The problem with dlist is that I'm using underscores as new lines. New lines become whitespace when they're stored in a variable. This is okay when those new lines began as whitespace anyway, but not when those new lines began as underscores. I'll see how I can fix this. edit: Furthermore, the until loop wasn't completing because I forgot the $ in [[ $dlist == "" ]]; I fixed it. The dates file now separates entries with whitespace or new line, and within entries you must use a greater-than (>) where whitespace would be. #! /bin/bash dlist=$(cat ~/astr/dates) echo "initial dlist "$dlist list="" until [[ $dlist == "" ]]; do ## Assigns the next value in $dlist to $date, then removes it from $dlist. date=$(echo $dlist | sed "s/-/z/" | tr " " "\n" | grep z) date=$(echo $date | sed "s/z/-/" | tr ">" " ") echo "date "$date dlist=$(echo $dlist | sed "s/-/z/" | tr " " "\n" | grep -v z) echo "dlist "$dlist ## Greps the table with $date, then isolates and assigns the longitude value(s). longitude=$(cat ~/astr/merc | grep "$date" | sed "s/\./\,/" | tr " " "\n" | grep [,] | tr "," ".") ## Appends $longitude to $list. list=$list" "$longitude echo $list done ## Indicate completion of the until loop. echo "List completed." Time for some math! Wooh! Not sarcasm! Again, I want some feedback on the idea of doing two binomial probability distibutions, one with more stringent success criteria, and then average their results. This is to give more weight to more exact "aspect" formations. The sad part is that this probably could be done more easily with arrays. Unfortunately I've never tried arrays in bash, and I never got them to work in C++. heh

Okay, this is bizarre. It's going down the entire ephemeris and printing all of the longitudes, repeatedly, endlessly, so the only way it ceases is with Ctrl+C. I decided to have the program read the dates off from a saved file, so they only need be entered once. The program is supposed to read each successive date by changing the first dash in the next date to a "z" by which grep can distinguish it, then removing that line with grep -v z. The z in $date gets changed back to a dash. In the dates file, the dates are separated by underscores which it translates to new lines. #! /bin/bash dlist=$(cat ~/astr/dates) echo $dlist list="" until [[ dlist == "" ]]; do ## Assigns the next value in $dlist to $date, then removes it from $dlist. date=$(echo $dlist | sed "s/-/z/" | tr "_" "\n" | grep z | sed "s/z/-/") echo $date dlist=$(echo $dlist | sed "s/-/z/" | tr "_" "\n" | grep -v z) echo $dlist ## Greps the table, then isolates and assigns the longitude value(s). $date is quoted so grep can handle whitespace. longitude=$(cat ~/astr/merc | grep "$date" | sed "s/\./\,/" | tr " " "\n" | grep [,] | tr "," ".") echo $longitude ## Appends $longitude to $list. list=$list" "$longitude echo $list done ## Indicate completion of the until loop. echo "List completed." I already copied the code to another laptop, and it had the same runtime error. If you want to run it yourself, however, it's real easy to do. Just put it in a text file, make it executable chmod +0111 /path/to/file then run it via the terminal /path/to/file

Article on the use of transcranial Direct Current Stimulation for cognitive enhancement http://www.oxfordmartin.ox.ac.uk/downloads/briefings/Mind_Machines.pdf

I'm not attaching electrodes to my head. ... or am I? http://www.bbc.com/news/health-27343047 No, I'm not. You're old. You go ahead.

The point is that recessive-dominance almost assumes that neither is silenced, unless there is some mechanism that consistently silences the recessive copy, thus making it recessive. If the dominant allele can potentially be silenced, then it isn't really dominant. Occam's razor would have it that both products are being produced.

They are, but as videogame controllers or brain-computer interfaces (BCIs). I'm sure people out there are placing electrodes against their skulls for transcranial kicks. https://en.m.wikipedia.org/wiki/Electroencephalography#Low-cost_EEG_devices

Even if it were suppression, the readers have the control in the long run. If the moderators allowed such content, fewer people would read read/join their site.

That's what DEF CON presentations are for. Presenting the malicious code will get a faster response than using the code in secret until somebody spots your hack, and it doesn't risk your reputation. Even Caudill & Wilson only released a sample code "into the wild" just to up the stakes for manufacturers; the original discoverers didn't release anything.

I was going to bring up X-inactivation, but that rules out recessive-dominance since only one allele is expressed for a given region of tissue.

I just vastly simplified the code by combining all those greps, trs, and seds into one line. Additionally, now it makes a list, which could be used for the math after the loop is terminated with "end". One problem: "end" doesn't terminate the loop. #! /bin/bash read date list="" until [[ date == "end" ]]; do ## Greps the table, then isolates and assigns the longitude value(s). longitude=$(cat ~/astr/merc | grep $date | sed "s/\./\,/" | tr " " "\n" | grep [,] | tr "," ".") ## Echos the longitude(s), then awaits user decision before appending $list. echo $longitude read decision if [[ $decision != "undo" ]] then list=$list" "$longitude fi ## Echoes $list for you to see. echo $list ## Obtain next date or end loop signal. read date done ## Indicate completion of the until loop. echo "List completed." Another problem is that $list is a string. During the math, the content must be read not as a string, but as floating point value(s). http://stackoverflow.com/questions/6348902/how-can-i-add-numbers-in-a-bash-script Before this can happen, I'll need to isolate the desired number from $list, which may require me to number the longitudes or else I'll need some sort of grep-like utility that relies on ordinal position. Here's an alternative version that numbers each successive entry. #! /bin/bash read date count=1 list="" until [[ date == "end" ]]; do ## Greps the table, then isolates and assigns the longitude value(s). longitude=$(cat ~/astr/merc | grep $date | sed "s/\./\,/" | tr " " "\n" | grep [,] | tr "," ".") ## Echos the longitude(s), then awaits user decision before appending $list. echo $longitude read decision if [[ $decision != "undo" ]] then longitude=$count"-"$longitude list=$list" "$longitude fi ## +1 count count=$(($count + 1)) ## Echoes $list for you to see. echo $list ## Obtain next date or end loop signal. read date done ## Indicate completion of the until loop. echo "List completed." Then the entries appear like this: 1-53.897867 2-183.3786478 3-321.6738923 One can grep the desired entry with the code below: floatingpoint=$(echo $list | tr " " "\n" | grep [$number][-] ) ## $number is the number of the desired entry. Putting the dash in brackets is similar to escaping it with the back-slash. Regarding the mathematics: At first I worried about getting the program to work in degrees, where 360 is followed by another 0. Fortunately, "aspects" and "orbs" are arbitrated differently from one astrologist to the next. Without excessive detail, an aspect is a specific longitudinal distance that, when achieved between two points or two celestial bodies, supposedly contributes to the effect. Examples include the conjunction (0°), trine (120°), and many more. The orb is the allowable error for a given aspect or celestial body. These are by no means fixed, so I think each user should arbitrate which degree ranges constitute a hit or a miss. This only allows for aspects between the celestial body's current position and the fixed "natal planets", but nearly all astrologists accept the validity of such, so it should be enough for a rudimentary test. Again, it will greatly simplify matters since the program will not have to do degree calculations. Furthermore we'll only be dealing with the relatively simple binomial probability distribution. I might let the user weight some hits differently since the conjunction (0°) and opposition (180°) are often considered stronger, as are more precise aspect formations. Unless there is a better way, I propose doing two binomial probability calculations, one with more stringent success criteria, and averaging their results.

If both are being used to make the protein which contributes to the phenotype, then I'd say yes. Forgive me for not having all the answers. A recessive allele may still be transcriptionally active, but the product is different such that it doesn't follow the same biological pathway to expression. For example sickle-cell is recessive even though heterozygotes have both types of hemoglobin. However if the protein product is the same, which it should for homozygotes, then I would think that both should be expressed unless one copy is silenced genetically.

x^a = 1/(x^-a) That would undefined with a zero. Imatfaal's explanation is way better.

Did you ever have one inside an MRI perchance?

I have my first question, so I might as well start the thread now. I began this project long, long ago, and I might as well complete it even though my interest has waned. I stopped looking at the planets' current longitudes to avoid bias, and I began writing down every day which I thought might be a Venus "transit" or Mars "transit". Two more analogous sets of dates were acquired from a journal I had kept for a few years. I won't share the dates publicly, but I'll share the results. In this instance, different outcomes for the different data sets could shed light on my bias. I also want to share the code, so testing these claims becomes easier for everyone. With such means freely available during my youth, I might have relinquished my belief sooner and with more confidence, and spent more time studying science! First question. SOLVED read foo until [[ foo == "end" ]]; do line=$(cat ~/Desktop/merc | grep $foo) line=$(echo $line | sed "s/-[0-9]\./--/") echo $line longitude=$(echo $line | tr " " "\n" | grep [0-9][.]) echo $longitude read foo done This is Bash code, what you type into the Linux shell. ~/Desktop/merc is the path to my plain text document downloaded from NASA HORIZONS. I only had #31 selected for table options.http://ssd.jpl.nasa.gov/horizons.cgi#top I need to assign the variable only the longitude. Unfortunately the longitude and latitude are sometimes indistuighablethe above code only works when latitude is negative. I might need a utility that prints a line based on its ordinal position. I am learning c++, so I might eventually include some of those libraries. Can anyone help? Okay solved it. The sed utility, formatted "s/input/output/", only changes the first instance of the input text. Thus I set it to change the first decimal-point to a comma, then grepped the comma. line=$(echo $line | sed "s/\./\,/") longitude=$(echo $line | tr " " "\n" | grep [,]) What comes next depends on how the math will be worked out, which I haven't attended to yet. I may have this script do the math, or I may have a separate script perform the math on its output. I only know some discrete probability, but math is where I excelled Will start contemplating the math.

I'm going to heaven! Okay, bye.

I recorded near a hundred dreams as a teenager, some taking up several pages, but I was never paralyzed. Sometimes I dreamed of awakening from a dream paralyzed, sometimes "waking up" a few times in succession. I would awaken finally after forcing movement hard enough to get my real body to move. Also interesting is that you can demand which type of sensory content is recalled from dreams. The visual content is fascinating.