Recent comments in /f/MachineLearning

Around-star t1_j4pk1lp wrote

Looking at the profiles of AI/ML Residents at apple, it is mostly PhD students, some with masters but did not find any holding only a bachelors. In that case, I should not have much hopes of hearing back :(

2

thiru_2718 t1_j4piklu wrote

Inresting question. My intuition if you could maintain a continuously-updated cache of the metric you're using to split your branches (i.e. continuously compute mutual information for each fork), and we assume your new data roughly follows the same distribution as your old data, you maybe able to get away with only modifying the downstream branches of your trees which should be more efficient.

But if that assumption isn't true, then the new data changes your trees closer to the root, and there's little benefit.

2

MegavirusOfDoom t1_j4pfdi1 wrote

Then we'd have to crawl all of stack exchange, all of wiki, and 1 terabyte of programming books... This "generalist NLP" is for article writing, for poetry.

I'm a big fan of teaching ChatGPT how to interpret graphs, the origin lines, to record in a vector engine that is couple with the NLP. For a coding engine, I believe NLP should be paired with a compiler, just like a maths specialized NLP should also have a mathlab type engine.

2

nmfisher t1_j4paqfc wrote

Easiest way IMO is to scan the list of papers at the annual conferences in your given field, pick a handful with names that sound interesting, then try and find a paper that's referenced by two or more of them.

That's probably a good place to start - it's been around long enough that it's probably not a flash in the pan, but still "new" enough to be relevant.

2

anothererrta t1_j4pagpo wrote

If you go to all this trouble, please keep in mind that electricity prices vary a lot across the world. In some places in Europe people pay twice as much as you assumed above.

Making it clear how you arrive at your value calculation in an updated post (or even making it a dynamic calculator where people can enter their cost/kWh) would be very useful.

2

TheTerrasque t1_j4p9kk7 wrote

There is a project called Petals that have BLOOM running for everyone to use. It's distributing the model over many machines and thus allows it to run on consumer hardware. There is a PoC chat at http://chat.petals.ml/

They just converted BLOOMZ and is currently setting up a network for that. That should be more suited for a chat interface. There's still missing gpu's though, so would be great with some more servers if people got some spare compute.

4

blackkettle t1_j4p8nqv wrote

It doesn’t seem to discuss the computational advantages in any detail. How interesting is this whole FF idea at this point? I’d love to hear more detailed analysis.

So far it seems like an interesting alternative but the “brain inspired” part is pushed in every article. In terms of accuracy it always seems slightly below traditional back prop. If there’s a huge computational improvement that would seriously recommend it I guess, but is there? Or is it just too early to tell?

9

__mishy__ t1_j4p5mm8 wrote

Completely agree, I would also add just a couple of tips I've found (not directly related to the question):

- have a good circle of friends in ML you chat to, you will sometimes find yourself in places where you are the only ML expert and you will need people you trust to bounce ideas across/tell you about new things you missed

- invest in a decent workstation and if you can't afford one try to get your first gig where it's not needed and buy one as soon as you can. This has saved me tons of time over the years

- get good at showing results quickly to stakeholders... and I mean you should be able to hack it in an hour at most. They are paying you a lot of money and want the feeling of progress. Something in slides/powerpoint is OK, a dumb streamlit/whatever app is even better. Impressing a stakeholder is the best way to get repeat work

5

Lethandralis t1_j4p15c3 wrote

This might not work if the cards have 6 degrees of freedom. You can check out CornerNet and its variants for anchor free corner estimation. The original paper detects two corners, but extending to four should be possible.

Another option is to use yolo to detect a rough bbox, and then use classical cv to refine corner locations.

2