Ensure you are logged in to the same iTunes account on your phone and watch. You can test whether your handoff is working by opening an email on your watch. You should see the email icon pop up in the lower left hand corner of the lockscreen on your phone. You generate a hexagram on the Apple Watch the same way you do in the main app: Once your hexagram is generated, it's shared via handoff with the Safari browser on your phone and, if you're set up to do so, the Safari browser on any of your Apple devices within range. Open the handoff link as you normally would by swiping up from your lock screen or clicking on the icon to the left of your Mac's dock.
Your particular reading, changing lines and all, will be there. When you are ready to generate a new hexagram, force-press the Apple Watch face to get the "Start Over" screen. If you would like to read more about the I-Ching, here are two great compendium sites and a few sources I really like: And for a handy step-by-step introduction to the yarrow stalk cast method, check out this great instructable.
- Smashwords – THE I CHING DODECAGRAMS. THE I CHING CODE - A book by Sergei Podoplelov - page 5.
- The Way Of The Chicken - A Guide To Keeping Backyard Chickens;
- Change Management - Averting the Chaos (Lance Winslow Executive Series - Change Management).
- Some changing lines don't make sense [Archive] - I Ching Community;
- Signals: Evolution, Learning, and Information;
You may also enjoy a piece I wrote on Medium, which Wired picked up: Behind the screen The I-Ching can be consulted a number of different ways. You're basically generating a random number from the set 6,7,8,9 to determine whether a line is broken or unbroken and changing or unchanging. But different methods yield different likelihoods, and the coin method, in which three coins are tossed, and the yarrow method, in which 50 yarrow stalks are ritually sorted, yield different results.
Depending on how you approach the book and its history, this is either a highly significant or a totally silly distinction. But as a math and coding challenge go, I saw it as essential that my app use the older, more complex Yarrow method. Here follows the manner in which the I-Ching was consulted by using the yarrow stalk method. The software abstraction of this process that I wrote in Jquery is available at GitHub.
If you would like a more pictorial step-by-step, check out HellaDelicious's instructable here. Remove one, set it aside. Randomly separate the remaining 49 stalks into two piles, East and West. Take one stalk from the West heap and hold it between thumb and forefinger of your left hand. Take stalks in groups of four from the East pile, until four or fewer stalks remain. Keep this remainder, place it between the ring and middle finger of the left hand. Take stalks in groups of four from the West pile until four or fewer stalks remain. Keep this remainder, and place it between the middle and forefingers of the left hand.
Your left hand now holds a sum of stalks equal to 9 or 5, being made up of one of the following possibilities:. If the number of stalks is nine, a value of 2 is assigned to this counting. If it was five, the number three is assigned. The 9 or 5 stalks are put aside. The rest of the stalks 40 or 44 by now are again divided into two piles and counted off as above. The possible outcomes this time are:. A 4 stalk remainder receives a 3. The four or eight stalks are set aside, and the remaining 36, 40, 32, or 38 stalks are again divided in two and counted off.
The possibilities are again:. It is these results which determine whether a line is solid or broken.
A 7 meant a strong, solid line. An 8 meant a yielding, broken line.
I-Ching: App of Changes
A 9 was considered a strong moving toward yielding line. A 6 was a yielding moving toward strong line. Like most westerners exposed to the I-Ching, I was taught the coin method of generating a line, which is far easier than the method above. By this method, three coins are tossed. Heads are worth 2, tails 3. The possibilities were thus:. This means, however, a slight difference in probabilities from the yarrow stalk method. However, the chance of a "Tail" on the first "Toss" in the yarrow stalk method is almost 3 to 1. Recall, the possible results for the first division of 49 stalks was this:.
Of four possible outcomes, three of them result in a 5, only one in a 9.
...life can be translucent
This means, in effect, that when we look to the lines, those generated by a 2 in the first place are less likely to occur than those that start with a It therefore makes sense that Yielding lines are slightly more likely to show up than Strong lines, and that a yielding changing line is the least likely all possible combinations to turn up.
This is because unlike the regular yielding and strong lines, the changing lines are each generated by only one possible combination of stalks. The yielding, changing combination, because it begins with 2, is therefore heavily disfavored over the strong changing line. Which is all just to say that the coin method does not hold the same built-in bias that the yarrow stalk method has. Surely note must have been made by the ancients that a 6 was a relatively rare occurrence indeed. Certainly, anyone in frequent consultation with the book by the yarrow stalk method would have noted the anomaly.
I noticed the reticence of 6 after many many runs of the developing program and thought my coding was somehow flawed. It became an app for iPhone, Android, iPad, and Apple Watch in , after a couple loyal users asked me to bring it out of the stone age and one extremely loyal user helped me unlock it from its floppy-disk carbon-freeze.
Here's the story of the software's beginning, from the original release of what was then called I-Ching. The full documentation of that project is available here. She had an absolutely gorgeous hard-cover copy of the book, three real Chinese coins, and made quite an elaborate ceremony of consulting it.
The book had a special pillow set up like an altar. There were candles, incense. I was skeptical about the whole thing, and raised a few Spockish Eyebrows, but the whole production was bewitching, and there was undeniable magic, even if the magic was nothing more than the good old alchemy of words.
Someone had just brought in a box before me which was still on the counter, unsorted. Lying on top was a mint condition copy of the Wilhelm-Baynes translation. Maggie looked at me with a cynicism-challenging smirk.
The ancient book of wisdom at the heart of every computer
I looked at my shoebox full of rat-eared paperbacks, picked up the beautiful hardbound I-ching and said "Trade? When I started messing around with computers in the mid 80s, the parallels between the I-ching and software kept jumping out at me. Both are binary systems, built of ones and zeros and yesses and nos.
What I didn't know at the time was there's actually a direct connection between the binary math that computers use and the book: The full title is translated into English as the "Explanation of the binary arithmetic", which uses only the characters 1 and 0, with some remarks on its usefulness, and on the light it throws on the ancient Chinese figures of Fu Xi. Leibniz's system uses 0 and 1, like the modern binary numeral system. Leibniz encountered the I Ching through French Jesuit Joachim Bouvet and noted with fascination how its hexagrams correspond to the binary numbers from 0 to , and concluded that this mapping was evidence of major Chinese accomplishments in the sort of philosophical mathematics he admired.
Leibniz saw the hexagrams as an affirmation of the universality of his own religious belief. I wrote my first tentative little bit of code to randomly generate six numbers, so I could cast the I-ching on the computer and look up the results in my book. Pretty soon I had a plan to create a full-blown program complete with my own interpretations, a journal for storing answers to questions, a lookup table for finding texts by hexagram, a user-definable colour scheme, a graphical menu system, and all the bells and whistles you could ever want from a piece of mids software.
I'd usually start coding around 7pm and hack away until well past midnight. Sometimes I'd spend the evening writing interpretations, sometimes it would be writing or debugging code. As I got deeper into the code engine, I discovered things such as the anomaly of the coin flip. At first, I started coding three variables to behave just like a toss of three coins, which is one method of generating a hexagram. But then I realised that statistically, this really wasn't even a close apporximation of the more ancient "Yarrow Stalk" method.
The coin method biased slightly away from changing lines all heads or all tails on the three coins. So I wrote a procedure that took variables separated into two random counts equalling the "East" and "West" piles of the 49 stalks, and sorted them back and forth in exactly the way an ancient chinese sage would have done. This little baby was a true 80s hepcat in usability terms. It used a clone of the VERY cutting edge Lotus menu system which I had to constantly recode because I kept forgetting to count from 0 instead of 1.
Learned a lot about arrays from that menu system.
I-Ching: App of Changes
My biggest constraint was it had to deliver on the media of the day, which meant I needed to cram more than pages of text, plus far too many thousands of lines of code, onto a single k floppy disk. I brought it in at zipped, a feat which still amazes me given some of the filesizes I was originally working with. The answer was my own compression engine.
It became clear after I was about a quarter way through writing texts that I would never get all pages down to size. Each of the hexagrams required the Judgment text, the Image text, and six pages of changing line text. Each page of text was around words. But I could store some of those words as abbreviations, and by storing such strings as "ing" and "ch" and "the" as single-byte tokens using the extended ASCII set, I could reduce thousands of instances of those strings from several letters to a single byte.
I became a compression maniac, trying to find sources for whether the word "that" or "which" was more frequent in the language to know which I should encode into my precious but limited trove of ASCII "Tokens. The I-Ching holds a litany of repeating phrases such as "It furthers one to cross the great water," and "Good fortune without blame. I ran the new code over the text and Whoompf! I remember doing a little Eureka dance on the empty Via Marmarata as I walked home at 3am, my head still reeling with code.
I published the final version in via one of the shareware forums on Compuserve. In those days, that was pretty good distribution. I also sent copies high and wide to friends and threw a few into the market at Porta Portese. It never earned me more than a few hundred bucks, but I had lots of emails of appreciation and enjoyed seeing it get mentioned in various news groups and forums over the years.
There were a couple requests and offers to help update it to a windows version, but I never got around to it. I still have most of the original source code, but one library got corrupted a couple decades ago, and the thing won't recompile anymore which is why my address still reads as Italy in the closing panel. Tauntingly, I have the full backup of the original work on a hard disk that came out of that old Compaq Sewing Machine it was written on, but in those days Compaq hard disks bore a proprietary BIOS wake-up routine, and the disk can't be accessed by slotting it into any other PC.
So until I dig up a working Compaq Portable II on Ebay and can resurrect the disk, the oracle is locked against revisions. That last bit prompted an email, out of the blue one day in , from Gary McCaskill, a former PC technician who told me he'd installed my programme on hundreds of computers he'd set up and made attractive with his own menus of shareware.
He had a specialty in data recovery, and could he be of help recovering the data? He rescued enough of the code to get me moving on the project. And when at one point I got stuck, unable to recover a swath of texts, he did a rather extraordinary thing. He reminded me that I'd built a backdoor into the programme -- one that I'd long forgotten, that would allow me to extract every text in the programme: I had all the material I'd written, and while it wasn't quite as structured as it would have been in code format, a few BBedit macros and a few late nights, and I had a complete XML file of text that had taken months of typing and creative hours.
So a huge thanks to Gary for prompting me to move ahead, and for using a rare set of skills in obscure s hardware to help chisel this fossil out of solid rock and breathe new life into it. Here's something Gary wrote me about participating in this project that made my heart brim: I'm 65 now, and I was talking to a friend less than a week ago about how much knowledge is lost to the world everytime a person dies.
Then think about a generation passing, and so much of the knowledge that was needed in their time just isn't needed. I watched my grandfather cast a babbit bearing with crumbled asbestos fibers and grease for a mold. Steam engine mechanics are gone forever. But that knowledge isn't required, and so it has to be dropped by each generation to make room for the knowledge of the times. And then I thought of the knowledge that I have that was essential for my profession 30 years ago, it's always the stuff that was inside a wide, flat, gray computer case.
Two of the very best are free. Sign up here to be notified when this is next available! I open for readings three or four times per year; you can sign up here to be notified when readings are next available. Please type these characters required. This field should be left blank. Quick search excluding the forums: Forum Shared Readings Results 1 to 10 of Thread Tools Show Printable Version. The questions were about relationships, so not work or health related. So I decided to ask what the 'something important' is and I got In some of the other threads regarding 22 it would seem that it's quite an interesting hex to receive and since I'm consistantly being informed of the something important returning, I'm rather intrigued by it appearing now How do you guys interpet this one?
Having read through a few translations and other threads on this, I think my answer lies more in the resulting hex, hex 24 Return. So who knows, maybe there's still a chance that I'll get back together with X. However, the Berkers translation puts it differently, in that, although "a friend returns" is mentioned in the hex text, the commentary says that I'm the one returning from what I was doing, for something better. I would appreciate some input on this from the forum Ignoring any traditional method use to get the patterns you have - lines 3 and 6 are controlled by hexagram