A while back I bought a LumoBack - a QS device that detected posture. Work on a lightweight strap with velcro strap around waist. Overall I liked it - especially when I realized that it counted steps pretty well, better in many ways than my Basis watch.
Unfortunately, I lost mine - I found it annoying to have the lightweight strap around my waist, when wearing an actual belt. I determined that I could take the LumoBack off the strap, and put it on my actual belt. Unfortunately, after a few days of doing this, with occasional buzzing reminded me to maintain good posture, I realized that the LumoBack had fallen off my belt. I conjecture that the plastic loops were stressed by the real belt, in ways they had not been with the original.
I would have bought a replacement, except the LumoBack was no longer for sale. It was replaced by the LumoLift, worn at the collar.
Received my LumoLift yesterday. First impressions:
---+ Overall Good
Nice small device.
Magnets hold it on through clothes.
Worn just under collar bone.
Advised not to wear on loose shirts. Has worked okay on all the shirts I have tried so far.
Magnets hold tightly enough that twice I have stripped off a shirt and tossed it into laundry hamper, forgetting to remove the LumoLift - and had to go dig in the hamper when I realized I was no longer feeling the occasional buss when slouching.
User interface on actual device good: double click to "snapshot", i.e. calibrate, triple buzz acknowledge; press and hold to toggle enable/disable buzzing when slouching, single buzz to acknowledge on, double buzz off.
In this respect better than LumoBack, where I frequently had to recalibrate using the Android app. Actually, the LumoBack had similar UI on the device, but I seemed to use the Android app most. It is a good thing that the LumoLift does not depend on the app as much as LumoBack did - since there is no LumoLift app yet.
The LumoLift seems less sensitive, out of the box, than the LumoBack was. Fewer false alarms; necessary because no Andoid app to control sensitivity. But it accepts slouched postures - I have to stand almost upside down to make it start buzzing. Perhaps when the app is available...
---+ No App Yet :-(
No Android app.
iOS app possibly available (unclear, I have no incentive to investigate).
Windows desktop app available "real soon now".
No Android app supposedly because Google Android's BLE (BlueTooth Low Energy) support is immature and unreliable. This may be consistent with the flakiness of the LumoBack, which required frequent resets.
---+ No Pedometerr ... ?
At least not until the app is available.
I liked the LumoBack enough that I would recommend getting it instead of an activity watch.
But the LumoBacl cannot play there.
---+ Non-standard USB Charging cradle
* I am annoyed that the LumoLift has a custom charging station - USB, sure. But this means that I cannot simply plug the LumoLift into whatever USB charger I have close at hand with a standard micro-USB cable - at my desk at work, at home, in car. Instead, can only charge up at one place.
Carrying around the charging station is suboptimal: since I have several such devices. E.g. my Basis watch.
Indeed, one of the reasons that I liked the LumoBack so much was that it used a generic microUSB charging connector. On several occasions I was able to charge it up, when my Basis watch was out of charge. Now my LumoLift and Basis watch are equally non-functional.
Buying extra charging stations - perhaps. After all, I have a total of 4 chargers for my laptop, albeit one being a universal (home, work, cottage, backpack). I used to buy multiple cell phone chargers, back when cell phones had proprietary chargers. But now that most cell phones have standard USB chargers, I just buy multiple USB chargers.
Perhaps it is good "gouge the consumer" marketing to require extra charging stations be bought by those of us who want ubiquity. Although, at the moment, you cannot purchase extra charging stations from Lumo. (I think Basis does sell extra charging stations, for a "gouge the consumer" price).
Although "do not ascribe to malice too quickly that which can be explained by stupidity". Or lack of standards.
Perhaps the designers of LumoLift and the Basis Watch realized that USB micro connectors are unreliable. Certainly an impediment to a QS deviced, that you might want to wear into the shower after a workout. (Easy to do so accidentally - I haven't yet forgotten to take off my Basis watch, but already, in les than one day of wearing my LumoLift, I have changed shirts twice without taking it off the old shirt. Which I think means that the LumoLift is non-obtrusive.
Micro-USB is unreliable. The Basis watch has 4 metal pads, the LumoLift two. Probably these connectors are more reliable. But they need pressure to make contact: on the Basis watch provided by a wraparound plastic cradle, on the LumoLift provided by magnets.
I am not aware if the LumoLift and Basis watch's power contacts are standard. Not found in a quick google.
I do rather wish that the LumoLift and Basis Watch had chosen to use the same sort of TRS connector (headphone jack, TRRS, Tip/Ring*/Sleeve, mini 3.5mm Apple, submini 2.5mm). Not standard USB, but reasonably common. Good enough that iPods can be made waterproof for swimmers.
I can understand that such a "shaft" may be a pain to design around. And that it is annoyingly thick. Still, I wish that the LumoLift and Basis watch used connectors that were reasonably widely available.
Disclaimer
The content of this blog is my personal opinion only. Although I am an employee - currently of Nvidia, in the past of other companies such as Iagination Technologies, MIPS, Intellectual Ventures, Intel, AMD, Motorola, and Gould - I reveal this only so that the reader may account for any possible bias I may have towards my employer's products. The statements I make here in no way represent my employer's position, nor am I authorized to speak on behalf of my employer. In fact, this posting may not even represent my personal opinion, since occasionally I play devil's advocate.
See http://docs.google.com/View?id=dcxddbtr_23cg5thdfj for photo credits.
See http://docs.google.com/View?id=dcxddbtr_23cg5thdfj for photo credits.
Tuesday, September 09, 2014
Monday, September 08, 2014
Thursday, September 04, 2014
These course notes are broken
'via Blog this'
Looks like course notes for a computer architecture parallel programming course.
Stupid quote: "LL, SC ... Unlike the RMW instructions, there is no need to lock the bus, yet it implements an atomic operation".
Apparently does not know that most advanced microprocessors have not "locked the bus" to implement atomic RMW instructions for decades.
Also does not know that a smart implementation of an atomic RMW is guaranteed to make forward progress - at ;east, the RMW instruction itself will complete - whereas LL/SC implementations are plagued by forward progress problems.
Instruction like this is one of the big reasons parallel programming advances so slowly.
Wednesday, August 27, 2014
Version control clean: unknown / ignored / skipped over
The reference is not what I am talking about in general, but an example
General - hg clean is pure evil:
'via Blog this'
Tools such as "hg purge" (or got clean)
have options such as
"remove all unknown files" (hg purge)
"remove unknown and ignored files" (hg purge --all)
Methinks there is a third option needed - not files that you have ignored because they are generated, but files that are skipped over, e.g. because they are controlled by a different version control system.
E.g. -X directory -- often I have a different VCS in the subdirectory, .bzr rather than .hg.
It is dangerous to type in "hg purge --all" in such a situation. E.g. it may delete the .hg/.bzr/.git subdirectories.
This is an example of "splitting": what is a simple action "exclude" from the point opf view of "hg add" is actually two flavors from the point of view of "hg purge".
General - hg clean is pure evil:
'via Blog this'
Tools such as "hg purge" (or got clean)
have options such as
"remove all unknown files" (hg purge)
"remove unknown and ignored files" (hg purge --all)
Methinks there is a third option needed - not files that you have ignored because they are generated, but files that are skipped over, e.g. because they are controlled by a different version control system.
E.g. -X directory -- often I have a different VCS in the subdirectory, .bzr rather than .hg.
It is dangerous to type in "hg purge --all" in such a situation. E.g. it may delete the .hg/.bzr/.git subdirectories.
This is an example of "splitting": what is a simple action "exclude" from the point opf view of "hg add" is actually two flavors from the point of view of "hg purge".
Thursday, August 21, 2014
Perforce Anti-Patterns --- labels
Perforce Anti-Patterns | Perforce:
'via Blog this'
While I agree with encouraging use of things other than labels (changesets, automatic labels, brancghes can all be equivalent for labels)
I think that calling this an anti-pattern is specious.
There are anti-patterns that are fundamentally bad.
But there are also anti-patterns that are bad just because of a poor implementation - and apparently Perforce's implementation of labels is poor.
Conceptually, a changeset is very much like a label - a set of files and versions, with comment metadata. (Again, using the "files at the bottom" mindset, which I don't like, but which I find easier to think about.)
Similarly, a branch is very much like a label - or, rather, the place on a parent where a branch starts.
These are similar conceptually, and probably should be interconvertible.
It is foolish to create a rather heavyweight concept like a branch, a contour, will do.
Perforce;'s slowness probably arises because it has a table that looks like
filename : version : branch-name
which grows as #Files*#Labels.
Even worse if the metadata is stored RCS like, replicated per-file. I can't imagine Perforce being that silly ... now ... although I suspect they may have been historically.
'via Blog this'
While I agree with encouraging use of things other than labels (changesets, automatic labels, brancghes can all be equivalent for labels)
I think that calling this an anti-pattern is specious.
There are anti-patterns that are fundamentally bad.
But there are also anti-patterns that are bad just because of a poor implementation - and apparently Perforce's implementation of labels is poor.
Conceptually, a changeset is very much like a label - a set of files and versions, with comment metadata. (Again, using the "files at the bottom" mindset, which I don't like, but which I find easier to think about.)
Similarly, a branch is very much like a label - or, rather, the place on a parent where a branch starts.
These are similar conceptually, and probably should be interconvertible.
It is foolish to create a rather heavyweight concept like a branch, a contour, will do.
Perforce;'s slowness probably arises because it has a table that looks like
filename : version : branch-name
which grows as #Files*#Labels.
Even worse if the metadata is stored RCS like, replicated per-file. I can't imagine Perforce being that silly ... now ... although I suspect they may have been historically.
Friday, August 15, 2014
Workflow is (almost) expressable as a Perforce branch mapping
Recently I have been working on a painful manual merge of some diverged, forked, documents. Painful because no automatic merge tools in Framemaker - I use compare documents, and then manually investigate diffs. (I remember doing this to the BSD 4.x kernel at Gould Real Time UNIX in the 1980s... gah!!!)
Key is developing a workflow: I assembled the files to work on in XXX.merge-needed.
I do my stuff, and then move the files to XXX.merge-pending.
In XXX.merge-pending, I wait to get approval, and then distribute stuff from there to unfortunately still replicated and forked source/destinatiions, call them XXX.fork1 and XXX.fork2. I also move my work item files to XXX.merge-done, once the distribution is done.
Editing of stuff in XXX.merge-needed is manual, as is moving to XXX.merge-opending.
But thereafter, it can be automated: when I have a batch of stuff in XXX.merge pending I can do
p4 cp XXX.merge-pending XXX.fork1
p4 cp XXX.merge-pending XXX.fork2
Key is developing a workflow: I assembled the files to work on in XXX.merge-needed.
I do my stuff, and then move the files to XXX.merge-pending.
In XXX.merge-pending, I wait to get approval, and then distribute stuff from there to unfortunately still replicated and forked source/destinatiions, call them XXX.fork1 and XXX.fork2. I also move my work item files to XXX.merge-done, once the distribution is done.
Editing of stuff in XXX.merge-needed is manual, as is moving to XXX.merge-opending.
But thereafter, it can be automated: when I have a batch of stuff in XXX.merge pending I can do
p4 cp XXX.merge-pending XXX.fork1
p4 cp XXX.merge-pending XXX.fork2
p4 mv XXX.merge-pending XXX.merge-done
Yes: I could be tracking the workflow in Perforce - even though IT discourages that.
The copy-copy-move script is *almost* a Perforce branch-mapping:
XXX.merge-pending/... --cp--> XXX.fork1/...
XXX.merge-pending/... --cp--> XXX.fork2/...
XXX.merge-pending/... --cp--> XXX.fork2/...
XXX.merge-pending/... --mv--> XXX.merge-done/...
Which would be nice - I could save it as a branch mapping, and reuse.
Almost but not quite - as far as I can tell, Perforce branch mappings really amount to "p4 cp", copies, buit do not have the ability to do moves.
Q: what is the difference between a script, copy-copy-move, and a branch mapping (extended to also do moves)?
The branch mapping is conceptually used to create a script of commands - but it also does various integrity checks. Plus it is transactional (at least I think that Perforce is transactional, ACID) - all succeed or none does.
Integrity checks, like ensuring files overwritten are not locked. It might be nice if it could be better - in this case ensuring that the destination files have not been changed since their common ancestor in the workflow loop. Which is basically a very simple merge or integration algorithm.
It is nice to have that sort of integrity wrapper around a script. It is a pain to code a script with all the necessary error handling.
I have long suggested that the folks who want transactional memory start by creating a transactional filesystem based scripting environment - for Perl, Python, whatever.
A DVCS is, in some ways, a mechanism that allows the user to create quite complicated transactions while disconnected, operating in a clone - and then later pushing, committing, rebasing or grafting. Interactive, because when a merge/integration fails, the user has to get involved.
Which would be nice - I could save it as a branch mapping, and reuse.
Almost but not quite - as far as I can tell, Perforce branch mappings really amount to "p4 cp", copies, buit do not have the ability to do moves.
Q: what is the difference between a script, copy-copy-move, and a branch mapping (extended to also do moves)?
The branch mapping is conceptually used to create a script of commands - but it also does various integrity checks. Plus it is transactional (at least I think that Perforce is transactional, ACID) - all succeed or none does.
Integrity checks, like ensuring files overwritten are not locked. It might be nice if it could be better - in this case ensuring that the destination files have not been changed since their common ancestor in the workflow loop. Which is basically a very simple merge or integration algorithm.
It is nice to have that sort of integrity wrapper around a script. It is a pain to code a script with all the necessary error handling.
I have long suggested that the folks who want transactional memory start by creating a transactional filesystem based scripting environment - for Perl, Python, whatever.
A DVCS is, in some ways, a mechanism that allows the user to create quite complicated transactions while disconnected, operating in a clone - and then later pushing, committing, rebasing or grafting. Interactive, because when a merge/integration fails, the user has to get involved.
Thursday, August 14, 2014
Versioned Label Sets
I like labels in version control systems. Like "Compiles". "Passes Tests". "Passes all tests except Test#44". Status if you will.
Of course, such status must be applied to set of files+versions. Or a repo-project-version. Whatever. (I will not use the whole-repo-project viewpoint here, since I am trying to think about partial checkouts. Whole-repo trivially fits - it is just a single entry, the rep version.)
You can think of a label as a file itself, containing a list of files and their version numbers. Such a label-file might also contain branch info, etc. - i.e. more metadata.
Generalize to an arbitrary package of metadata associated with a set of files+versions. "Labels" may be such that their name is the only metadata that matters.
Such a label-or-metadata-file can itself be versioned. Must be, should be.
In fact, just about everything we care about can be considered a set of objects+versions, in a file, itself versioned.
Branches may be defined by rules such as a list of filenames or patterns. Possibly with versions that are frozen in the branch.
OK, there is a difference: branch histories are graphes. Steps along the history are the sets of objects+versions that most closely correspond to a label set.
I.e. there are graphs whose nodes are objects+histories.
Anyway... : the default action is where the difference arises.
When a workspace is checked out from a branch head, when trying to check in the default is to extend the branch.
When a workspace is checked out from a label, the default is not to extend. The label.
We can imagine interconversion: forcing a checkin to a label, making the label into a branch.
---
Who stores the linkages?
Label-sets may be marked inside a branch-graph file, or outside.
Outside allows non-privileged access. Library users can label library versions.
Inside may be faster and more convenient.
It is important to be able to track the configuration of stuff that you are not allowed to write into the "home" VCS for.
The DVCS people say "just clone", but that may not always be possible
I may want to have a local repo, linked to a master repo without incorporating all, and be able to define cross repo actions.
Subscribe to:
Posts (Atom)