bwindsor

Location: UK remote

Remote: Yes

Willing to relocate: Not immediately

Technologies: Python, AWS, Docker, Typescript, React, CI/CD, C (ESP32), Matlab. If I don't know it, I can learn it.

Résumé/CV: https://www.linkedin.com/in/ben-windsor/

Email: benwindsor at gmail.com

Software & Algorithms Engineer with 10 years experience bridging the gap between robust, scalable production software and complex mathematical modelling. I have lead the architecture for IoT systems, developed energy-constrained algorithms, and mentored individuals within cross-functional teams. I enjoy challenging, varied projects and am keen to further expand my leadership and technical expertise. I'd like to see my work out in the real world making people's lives better.

If all the stuff you want to ignore is inside another folder, you can create another .gitignore inside that folder containing just * (i.e. ignore everything). Everything including the .gitignore file itself will be ignored.

Thanks for that feedback - the product is basically ready to go, the reason for Kickstarter was to get pre-orders to get enough capital to pay for a larger manufacturing run. Of course, it's quite possible to take pre-orders without using Kickstarter, so that may be a better route.

At our company we have built a device which monitors your stove with an IR sensor and has an alarm for dangerous situations [0]. It does some processing on the sensor data - if it detects a dangerous situation it beeps loudly and sends you a text/call in case you are out. It can also guide you through recipes, currently there's only a small handful though [2].

We aren't entirely sure how to market it successfully though (there's an alternative landing page [1]), and the chip shortage is also affecting our ability to manufacture.

[0] https://mypippa.me/

[1] https://mypippa.me/pippa-saves/

[2] https://recipes.mypippa.me/

It doesn't know which smoke point to monitor for. However, the aim (at least for the MVP) is for it to work the majority of the time for the majority of users - and critically to alert several minutes before there is any flame. So while sunflower oil may start smoking a small amount, it would be several minutes more getting to flame, by which time the alarm should have sounded.

If you put a frying pan on with oil in and leave it, the device will alert you at around 450F. This is a fixed threshold (along with some other checks, e.g. we also consider the rate of change of temperature). This gives reasonable behaviour in most cases, and ensures you don't get nuisance alarms when frying on high heat. In cases where individuals have an unusual cooking pattern which causes unreasonable false alarms we can adjust the model parameters to increase/decrease sensitivity in particular situations. In the future we may be able to adjust these automatically but for now there is not a great deal of automated "learning" involved.

If you're a pyromaniac chef, I think you would get some alarms from that! Again this is a bit of an edge case so we haven't but much effort into that for the first iteration of the product, definitely something for the future though - I can imagine it being a challenge to distinguish flambee and a real fire though, since flambee is real fire!

Thanks for the suggestion! We did consider the idea of making it automatically cut the energy source. However at the moment, the install steps are: receive it in the post, pull out the battery tab, and stick it on your stove splashback with a strong sticky pad. Almost anybody can do it themselves. As soon as you need to cut the electricity/gas it requires a qualified engineer to go in and install it, making the install cost an order of magnitude larger. So this wouldn't be a part of the core product.

As an optional paired peripheral, it's a good idea, and perhaps we will look into it further if the main product has some success. If individuals consider it a valuable addition then they could pay to have it installed. A secondary drawback would be reduced battery life on the device, as it would be continuously paired over Bluetooth whenever the stove is in use - usually it is just passively advertising in case you are trying to connect through the phone app.

In terms of saving lives, the automatic cut-off would make a relatively small difference - fire department stats (on smoke alarms) show that having a loud beeping alarm is extremely effective at attracting attention and is enough for the user to go and turn it off manually, or to get out of harm's way if things have turned bad. Where the automatic cut-off would help is in reducing the chance of the house being damaged by smoke or fire when the user is out of range.

I'd be interested if there's research showing whether a one-off popup gives more signups or more annoyance. The marketing people seem to think it's better to have it there.

I agree it's hard to close, I'll see if I can do something about that. It shouldn't keep coming back once closed, which browser are you using? Although it does come back if you refresh the page. I might be able to do something about that as well.

I've been working on a stove safety/smart cooking device which is based on the temperature of your pan [0]. There are a small number of recipes which it currently works with [1]. To do this we defined a JSON format for recipes [2] but if we could use something similar to the text format used by CookLang that would be amazing, as it's much easier to write than JSON and could also be automatically rendered into a web page. Currently we are writing it twice - once in JSON for the cooking app, and once in human readable form.

[0] https://mypippa.me/ [1] https://recipes.mypippa.me/ [2] https://recipes.mypippa.me/schemas/cookMLSchema3.0.json

Or use secrets.token_urlsafe https://docs.python.org/3/library/secrets.html#secrets.token...

Skyrad Ltd. | Algorithm Inventor | London, UK | ONSITE, FULL-TIME |

Skyrad invents products in the rapidly developing IoT and energy sectors. We're currently analysing how monitoring heat and acoustics through various means, including using computer vision in the infrared part of the spectrum, can reveal patterns which let us discover and predict faults, risks and inefficiencies in systems. We take brand new technologies from prototype to patent and to market. One of the products we invented is LeakBot (www.leakbot.io).

Looking for excellent numerical skills, preferably with a background in algorithm design such as signal or image processing, control engineering or machine learning.

Preferred technologies:

-Matlab/Simulink

-Python

-SQL

-Experience in rapid prototyping e.g. Raspberry Pi

-AWS

Excellent work-life balance, hours are flexible, working remotely from time to time is fine, near zero office beaurocracy.

More: https://www.linkedin.com/jobs/view/algorithm-inventor-at-sky...

Drop me an email and CV on ben.windsor {at} skyrad.co.uk if interested

The final MATLAB example of "Inplace modification" is not correct.

  function f(out, x)
       out = x.^2
  end
  x = rand(10)
  y = zeros(length(x), 1)
  f(y, x)

What happens here when you call f(y, x) is:

1. The arrays x and y are passed to f (no memory copying done yet, since MATLAB uses copy on write)

2. When we have `out = x.^2`, this will allocate a new array in memory and store in it the result of `x.^2`, and will call this `out`. The original `out` which was passed into the function can now be garbage collected (although it won't be, because it's still in the parent scope as 'y')

3. When the function exits, the new `out` goes out of scope and can be garbage collected.

So all this example does is allocate a new array, assign x.^2 to it, and then throw that result away again. There's no in-place modification.

You can't really pass a matrix by reference in MATLAB like you can in Python, however in some cases you can write your function in a specific way which will ensure in place operations are done and prevent a huge matrix copy. For example (pauses are just there so that you can watch task manager memory usage):

  function x = inPlace()
      x = rand(100000000, 1);
      pause(3);
      x = doSomething(x);
      pause(3)
  end

  function y = doSomething(y)
      y = y.^2;
  end

Conditions required are:

* Input and output variables must have same name in caller

* Input and output variables must have same name in callee

* Callee must be inside a function, not a script

Look here for a more detailed description: https://blogs.mathworks.com/loren/2007/03/22/in-place-operat...