Briqs locations3/30/2023 While ice cream shops are kid-friendly by nature, BRICS is especially so with great people watching on the trail, some books and crayons in the shop for speedy eaters, and a casual atmosphere with a great selection of ice cream. Stop in after school (Tuesday, Wednesday, and Thursday) and bring your homework to get 50% off of the student’s purchase. This cute little shop right on the Monon Trail sells ice cream, hot chocolate, lattes, s’mores, and other delicious treats. Totally worth it on a hot summer day! Our flavors of choice were Chocolate, chocolate chip cookie dough, Show Your Colors and Monon Tracks. However, if you want to be really green and have nothing left to throw away, grab a cone!īrics opened in July 2010, and has since offered a special place for families to step off the Monon and relax on their deck with a cold treat or something to drink (there’s a water station to refill your water bottle)! The four of us enjoyed ice cream for just under $20. My ice cream came in a paper cup that was recyclable and fully compostable. The building is reminiscent of a train station and it’s located right on the Monon trail near 64 th street.īoasting more than 35 different flavors of ice cream with all kinds of cones: waffle, chocolate dipped, dipped with sprinkles and so on, BRICS has something for everyone. If the name doesn’t scream this to you, BRICS is located in Broad Ripple. I’ve added some documentation on how to track changes in the development branch.Looking for the best ice cream in Indy? We’re doing the hard work of checking out all of the Indianapolis area ice cream hot spots and today we visited the Broad Ripple Ice Cream Station, also known as BRICS. The “develop” branch is already moving ahead:Īs you can see, it’s all made up of “briqs” which can be added and enabled as needed. Let’s see how it evolves, and please do comment and hack on it if you are interested. Which is all a long-winded way of saying that HouseMon is still in its very early stages. There is currently very little error checking and error messages can (will!) be cryptic. Part of the process is getting to grips with complexity: multiple sensor values per reading, “de-multiplexing” different types of packets from the ookRelay, mapping node ID’s to locations, ignoring some repeated data which contains no extra information, and more real-world messiness… This diagram is still too complicated for my tastes. The dotted lines indicate that logged and archived data is being saved but not used yet (logged data is the raw incoming text from serial interfaces, etc – archived data is per-sensor information, aggregated hourly). Here’s an attempt to map out what’s in the 0.5.x release: There seems to be no other way to go through this than just bite bullet, get a basic release out in the wild, and see how it holds up when installed in more places. I suspect that this project will lead to more questions than answers at this stage, but I guess that’s what you get when following the “release early, release often” approach of open source software. After that, all web accesses will be a lot snappier than in development mode.īut let’s not get ahead of ourselves… tons of work to do before HM becomes useful! To get an idea of the true performance on a Raspberry Pi, you should start up as follows (make sure HouseMon is not running already): cd ~/housemon & SS_ENV=production node app.js – this’ll take a few minutes while SocketStream combines and “minifies” everything the first time around. Note that the instructions so far were all about development. It feels a bit odd to give this piece a software a version number, since it’s all so early still, but I’m releasing it as HouseMon 0.5.1 anyway, to set a baseline for future development.
0 Comments
Leave a Reply.AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |