Feb 22, 2018

Water hardness test

Summary

I tested with the following product of water filter, comparing to Tube water (control group).


As a environment we use a water case from PearlCo and this reagent for water hardness.


Test protocol is as follows :
  • Repeat followings for each group
    • Fill out test tube with filtered water to 5 [ml] mark
    • Add titration solution drop by drop the while swirling test tube
    • Count drops until color changes from RED to GREEN 
  • Since 1 drop of reagent express 1 degree dH (see the measurement), calculate each hardness.

The result shows Tube water is 14, BRITA is 8 and PealCo is 4.

According to this Hard-soft classification table, each shows “Very hard”, “Hard” and “Moderately hard”.
Since I use the same environment ( water pot ), I should use PearlCo as long as I want to avoid drinking hard water.

I cannot rule out the possibility just by this trial:

a filter from the same maker as water pot may enhance effect of filter.
Because they can fit each other rather than other makers.


Drop count
Tube water
BRITA
PearlCo
0
1
SKIP
2
3
SKIP
4
5
SKIP

6

7
SKIP

8
SKIP

9


10


11


12


13


14


Feb 3, 2018

give unique identifier to show the same files differently in org-agnda

I'm a big fun of org mode. But I have the one problem with this mode.

When you register two files, a/readme.org and b/readme.org to register org-agenda-files, the problem is that o, both are expressed "readme" and treated as the same agenda.

Imagine the case where you join two different project for development, you will see how annoying those are. So I tried to solve this problem.

My basic idea was to use the upper directory name also as an identifier. In the above example, "a/readme" and "b/readme" show up in Org Agenda and are treated as different tag space.

It was also nice to know how to debug functions in emacs / elisp.

example

before fix

readme    :TODO [#A] update docs for sound-reflection module
readme    :TODO [#A] update docs for setup

after my fix

ultrasonic/readme    :TODO [#A] update docs for sound-reflection module
onboarding/readme    :TODO [#A] update docs for setup

implementation

I checked where the value comes from in org-agenda.

files

set up edebug to trace a

edebug is simple to use so this matches my case.

  • enable edebug-defun to target function
  • enable breakpoint by C-x X b
  • enable edebug-step-mode
  • run function
    • you can eval / step /continue