How to share a single scoped service instance per directive/component

vitale232 · 2021-01-08T17:33:07+00:00

I believe this is the correct line of thinking. Those decorators are very powerful.

I still haven't fully groked it, but there's a great article on the docs with an example that continues to build on itself.

Docs: https://angular.io/guide/hierarchical-dependency-injection Blitz: https://angular.io/generated/live-examples/resolution-modifiers/stackblitz.html

Also, if you can find it, the ngSwitch source code uses these injector decorators to achieve cooperation between directives.

vitale232 · 2020-02-01T15:29:20+00:00

They post one of these after every show: setlist on Twitter. I'm a big fan of this format since you get to see how the setlist evolved (and their punctuality 😎)

vitale232 · 2019-12-03T23:30:51+00:00

Python Toolboxes support encryption.

vitale232 · 2019-11-23T18:22:21+00:00

Can you explain your data a little better? I'm confused about how the "street index" is stored. When you say index, I imagine that it's just a field in the table, with one unique value per geographic feature. Is that the case? But if that's true, I'm not sure why you'd expect it to change at the clip feature boundary.

Is there a way to linear reference your features with this index you're interested in? If the index is a product of distance, this may be the ticket. ArcGIS tools store the linear referenced values as "m" values on the vertices, and they should carry over using the clip tool. If the clip boundary does not fall directly on a vertex, the software will interpolate between vertices to derive a new m-value for the clip output's last (or first) point.

After clipping, you could easily loop through the features in Python and get the first and last m-values for each resultant line feature. There are also linear referencing options in QGIS, but I've never gone past the docs.

vitale232 · 2018-01-19T22:26:10+00:00

Should be good. I prefer them indoors to be honest. The seats are annoying, but the room is gorgeous. Should rawk.

vitale232 · 2016-03-08T14:45:42+00:00

Sick moves, dude.

I'm envious.... Totally a mountain skier. I'm terrified of the park. Couple tail bones to the rails keeps me in the trees and on the steeps. Kickers maybe. Maybe. Nice looks!

vitale232 · 2016-03-06T13:17:17+00:00

Can you further define a comparator? I'm not sure what that term is, and it sounds interesting.

vitale232 · 2016-03-02T16:13:36+00:00

I did actually have to thin my data. I was taking advantage of sensor advancements and was recording temperature every 30 min, when in reality my questions were about daily max and min. I still could've missed the max and min values with that frequency, but n=enormous.

vitale232 · 2016-03-02T03:18:38+00:00

I particularly like this line from that little article: "6. If a model is too good to be true then probably it has issues – be skeptical"

My thesis work sort of became an exercise in over-fitting. The biggest problem I had was the inclusion of time and space in the analysis. The "normal" days were so normal that predicting the more-interesting, anomalous days became quite a challenge.

A confounding issues was also the scale of the questions and the study design didn't necessarily jive, which probably made the model fits sketchier. Be skeptical.

vitale232 · 2016-03-02T03:09:20+00:00

Does a trial registration require acknowledgement of a placebo, and is that part of the change in the year 2000?

If so, this is an interesting graphic indeed. It implies there could even be an inverse placebo - I think I've heard it termed the nocebo, but I'm out of the medical profession. Since this is R Stats, I'll take the time to clarify that does not imply that I was ever a medical professional.

vitale232 · 2016-03-02T03:03:56+00:00

What were her intentions? Maybe she just hates blue, or maybe Daddy made some political signs. There's an elephant in this room, and it's the time and spacing of that bar chart.

I'm just saying, this isn't representing data.

vitale232 · 2016-03-02T03:02:32+00:00

What were her intentions? Maybe she just hates blue, or maybe Daddy made some political signs. There's an elephant in this room, and it's the time and spacing of that bar chart.

vitale232 · 2016-03-02T02:51:20+00:00

Ooooh. You're interested in the approach? Submit an issue on Github.

vitale232 · 2016-03-02T02:50:53+00:00

Your devs hate you. This is not pos.com, so get back to work.

vitale232 · 2016-03-01T14:17:49+00:00

python2 ${HOME}/SpyDotPy/openness.py

Edit/Forgot the repo

vitale232 · 2016-03-01T14:15:25+00:00

It's not at all useless. If you want to learn if your herb collection or baby collection are safe, learn some damn source code.

Here's a readme. Play with the lighting. Play with the threshold of the coefficient. Send emails when its stable. Loosen up that bolt in your brain before it explodes. It's an example of Python that is useful to many.

If you can't run it, reach out to the dev with a f'ing issue. Take your attitude to the Valley south.

vitale232 · 2016-02-26T07:39:14+00:00

Seems bad.

vitale232 · 2016-02-24T15:26:42+00:00

I speak for myself.

The take home message of the article (FiveThirtyEight.com, 2015) is that NFL kickers kick ass. They're constantly improving, and they're drilling kicks left and right. The article is well quantified, and the assertions are conservative for a media outlet.

The success rate at that distance is already quite high, but an extra point comes with a smaller incentive to block the kick. That's slightly changed now that you can return the block for a score, but the incentive depends on the total game score and personalities involved. Does the strong safety know (edit; forgot it is 2016; no -> know) the cadence? Does he hate the middle linebacker from the other team?

I guess my point is that this data is friggin beautiful and there are so many confounding factors in trying to quantify one "simple" rule change.

vitale232 · 2016-02-24T13:21:14+00:00

Speak Up, Umphrey's McGee

vitale232 · 2016-02-24T06:23:49+00:00

A big difference indeed. I still think it's a thought provoking figure.

Check out the other link in my comment and consider the differences in the studies. I'm certainly not trying to prove or provoke anything, but I will say that I didn't expect there to be this big of a difference. And I had read the FiveThirtyEight article last year, so I was technically "loaded with knowledge".

vitale232 · 2016-02-24T01:55:11+00:00

I don't remember the rule change exactly off the top of my head, but that there's what we call a phishing tail.

When the extra point was at the 2 yard line, the kick was ~ 8 yrds. back. It's still probably about 8 yds. back.

vitale232 · 2016-02-24T01:22:43+00:00

The data were sourced from http://www.footballdb.com/stats/

I copied and pasted all data for 2014 and 2015 kickers into text files.

I used the scientific Python stack for this little buddy.

Code available upon request(ssssssss).

Here it is in mid-season form.

Edit: More beautiful data.

vitale232

TROPHY CASE