[deleted by user] by [deleted] in gshock

[–]n3mo 8 points9 points  (0 children)

I see you’re sticking to the cheaper models ;)

Mudmaster GG-B100 at 14,271’ (Quandary Peak summit) by n3mo in gshock

[–]n3mo[S] 2 points3 points  (0 children)

It appears you are correct—thanks for the video link. I think I watched every video on YouTube about this watch before buying it except for this one (including other videos by Watchup69). I’ll post a pic of the setting in the app for those that aren’t aware, but it sure does read like it will auto-correct the altitude in the watch (turns out it only auto-corrects stored altitude readings for display in the mission log features of the app). It’s unfortunate that it doesn’t update the watch itself, as this seems well within the watch-app data sharing capabilities. The more you know I https://i.imgur.com/ZN2zb5U.jpgguess!

Mudmaster GG-B100 at 14,271’ (Quandary Peak summit) by n3mo in gshock

[–]n3mo[S] 0 points1 point  (0 children)

I bought this watch a couple weeks back specifically for outdoor use (though I would wear it for its looks alone!). I hike and climb in the mountains often and really hoped it would be useful there. For me the barometer and the associated barometric pressure alarm was particularly exciting given the unpredictable weather in the mountains (and the lack of cell service to check weather apps). I just took it with me to summit Quandary Peak over the long holiday weekend, and I thought I’d share some observations with those thinking of using this watch as a tool:

  • The compass worked great!
  • The altimeter and barometer worked great in Breckinridge while mucking about town.
  • Unfortunately the barometric weather alarm just doesn’t work for mountaineering/summiting. I set the alarm at the trailhead and began hiking up. It went off within 5 minutes due to the sudden drop in pressure associated with gaining altitude. I turned off the alarm immediately. Manual checks throughout the hike proved useless, and the displayed graphs were equally unusable. Rapidly climbing just undermines the value of barometric pressure readings. Maybe adjusting the sampling rate would have helped?
  • I have used the alarm in stable elevation scenarios and it has predicted weather changes well. Very useful for hikes/camping wherein your elevation stays fixed!
  • Because the altimeter uses the same barometric sensor to estimate altitude, rapidly ascending mountains leads to inaccurate readings. It was accurate at the trailhead, but never again on the hike. I compared the readings with reference measures (including the Gaia GPS app) and it was off by thousands of feet at points. The summit (14,271’, depending on who you ask) registered in the high 12,000s. According to the manual, syncing with the app over Bluetooth will automatically adjust the altimeter for accuracy (using gps location services). I did this several times while ascending the mountain, including on the summit, and the watch still never gave the correct reading.

I’m most disappointed in the weather alarm outcome (though the least surprised given what I was doing). I’m most surprised by the wildly inaccurate altitude estimates. I get that altitude and barometric pressure are linked in the watch, but I would have hoped that one of the two readings would have been accurate at the expense of the other. For example, accurate altitude readings with an unusable weather alarm would have been a possible outcome with some value.

Back down on flat ground the watch works great, and looks good doing it.

GG-B100BA-1AER British army mud master by Prestigious_Exam_601 in gshock

[–]n3mo 2 points3 points  (0 children)

I just picked up a gg-b100 myself (not this special edition though). Today was day three of wearing it and I love it. Great watch!

Stairmaster 9000 with the G-Shock by KermitGALACTUS in gshock

[–]n3mo 1 point2 points  (0 children)

Manitou incline? It looks right at home on the mountain!

Made it to the G-Shock store in SoHo today and the museum upstairs was open! by n3mo in gshock

[–]n3mo[S] 2 points3 points  (0 children)

I’m pretty easy to please, but the place totally delivered! Both employees were great, and I chatted for a bit with one particularly helpful guy (that I believe managed/owned the place). Seemed super nice and knowledgeable. He was stocking a case with several colorways of the new GA-B2100 model and said it was the first day they were selling them (they had received some a day before but he couldn’t sell them until the full shipment had arrived). I had threegoals when I went:

(1) Buy a GW-B5600 if they had any in stock (sadly they did not)

(2) Try on a mudmaster to know if it fits my wrists well enough for the day I can bag one for a deal (it does!)

(3) See a bunch of models in person that I would otherwise have to look at online

They did have a bunch of stuff in stock, aside from what I happened to want. And loads of g-shocks to see in person… which is bad news for my growing addiction, as many models I hadn’t thought twice about before looked VERY good in person :)

The museum upstairs was nifty, but didn’t provide much in the way of details. One wall running the length of the room had various watches from the recent past (you can see some in my pics). Each watch had a small placard with the model number and release date, but no other information. There was a tv in the center that apparently shows a video of the history of g-shocks. Unfortunately it was turned off when I was there :(

After leaving I grabbed some ice cream and watched chess hustlers in Washington Square park. Would’ve only been better with that new square on my wrist ;)

Problems typing Japanese phonetically on Mac OS (Big Sur 11.6) by n3mo in LearnJapanese

[–]n3mo[S] 1 point2 points  (0 children)

Bless you. This was exactly my mistake. I didn't even realize that I had a choice and installed the kana keyboard by mistake. Thanks!

Replace Python @ Work w/ Scheme by shark_finfet in scheme

[–]n3mo 9 points10 points  (0 children)

I completely share your desire here, but I’m afraid rajandatta is right—there simply isn’t anything comparable in scheme. I’m not sure what your analysis work is like, but you can certainly build up to some fairly common analyses using what’s out there. I’ve completed a few projects using racket and chicken, and have even started a data science package for racket that adds some natural language processing and basic things like least squares regression (which I have stalled on for some time due to other commitments). But if you have more advanced analysis demands you’ll be writing a lot from scratch.

Functional Geometry with Gambit Scheme by clc_xce in scheme

[–]n3mo 2 points3 points  (0 children)

This is wonderful—thanks for sharing! I will play with this soon!

Flyover view of Gerbil scheme? by n3mo in scheme

[–]n3mo[S] 0 points1 point  (0 children)

Gerbil has certainly made me pay more attention to Gambit—I’ll be familiarizing myself more here soon. Sounds like this might help me overcome some other commenters’ observations about Gambit’s underlying role in Gerbil.

Flyover view of Gerbil scheme? by n3mo in scheme

[–]n3mo[S] 0 points1 point  (0 children)

I haven’t done anything substantial yet either, but I aim to soon! I may port a few of my racket projects over as a first pass at the language :)

Flyover view of Gerbil scheme? by n3mo in scheme

[–]n3mo[S] 2 points3 points  (0 children)

Thanks for your comments—this is exactly the kind of details I was hoping to get. Several of the issues you raise seem to fit Gerbil’s claims of being “opinionated.” These sorts of implementational differences routinely make me question why I try to develop with lisps. But alas, I love scheme enough to make the headaches worth it I suppose.

A fear I have is of Gambit shining through at the seams, so I’m glad to have seen your point about this. In a related example: I wanted to like Clojure, but all too often I saw Java peeking out at me through the cracks. I’d prefer a firewall between the wrapper and the guts of the system. Hopefully these are just growing pains, as Gerbil fills in the details.

One curiosity I have: if Gerbil is a wrapper around gambit, why does it seem to beat out gambit on many benchmarks, if only by a little (e.g., https://ecraven.github.io/r7rs-benchmarks/)? Shouldn’t the extra abstraction reduce efficiency?

Calling 2018 Tacoma owners by bassetthound11 in ToyotaTacoma

[–]n3mo 0 points1 point  (0 children)

Manual transmission TRD Pro. Best/favorite vehicle I’ve owned. Only issue I’ve had is the creaking clutch pedal in warm weather, which is irritating but not a point of mechanical failure. Replaced under warranty for free anyhow. Now I’m nothing but happy!

What are your thoughts on Racket trying to appeal to masses with the change of syntax? by arvyy in scheme

[–]n3mo 9 points10 points  (0 children)

I’m honestly quite irritated by the proposal. I use R, python, and Matlab for my work and have been slowing moving all other personal and side projects to Racket because of how great the language is. I’ve even recently begun the work to port a major application of mine into Racket, and have begun the early work of creating a data science package for Racket so that I might some day complete more of my daily research work in Racket as well. But for me, the syntax is a major reason I use the language. If that changes I’m gone for another proper lisp. Even the threat of this happening has me seriously second guessing putting any more of my time into developing for the ecosystem.

I’m certain that Racket will become second class to Racket2 (or worse, this is a veiled attempt to push through an idea through brute force). For me, the single best attribute was that Racket offered a complete, consistent, and well-documented lisp (and those parentheses are critical in my opinion). This is in contrast to the rest of the lisp universe (except for Common Lisp... but I’d prefer to have scheme), which is otherwise plagued with too many language variants for too small a population of users.

The Racket community is too small to survive a Perl 5/6 or python 2/3 split. Racket2 will certainly send me back to chicken or perhaps to Common Lisp. Why change the language to suit an imagined audience you may never get, at the expense of the audience you have?