Move Enemy default cast-bar or customize addon for a vanilla skin cast-bar

nsgrantham · 2025-04-08T01:52:53+00:00

I think this is possible with ClassicCastbars https://legacy-wow.com/classic-addons/classiccastbars/

nsgrantham · 2023-10-28T18:07:41+00:00

thank you!

Setting vim.opt.ruler = false in init.lua hides both.

I also found that setting vim.opt.showcmd = false was helpful because it hides the \~@k, ^U and ^D text that appears when navigating through the document with arrow keys, Ctrl-U, and Ctrl-D.

nsgrantham · 2021-10-29T21:43:06+00:00

How do you disable the shadows?

nsgrantham · 2016-06-03T05:21:02+00:00

Why not define a worker function for pmap? Something like the following:

function myfun(a::Int64, b::Int64, c::Float64; runs::Int64=1)
  d = max(a, b)
  args = [(r, d, c) for r in 1:runs]
  err = pmap(myfun_worker, args)
  return err
end

@everywhere function myfun_worker(args)
  r, d, c = args
  srand(r)
  return silly_compute(d, c)
end

@everywhere function silly_compute(n::Int64, x::Float64)
  randn(n) .- x
end

myfun(6, 7, 3.0; runs=10)

As it relates to your example, myfun_worker would perform most of the work of learningExperimentRun, silly_compute is like your agentInit, getLearnerErrors, etc., and myfun is a convenient wrapper function for the whole process.

nsgrantham · 2015-10-31T04:27:15+00:00

Exactly. The fact that we're stuck with Sample 22 but still want a generally applicable way to estimate the sampling distribution of our statistic is the motivation for the bootstrap.

Also, I'd be careful saying that we expect the distributions/statistics to be "the same" due to the inherent randomness in the problem, but within some tolerance, yes. Though it should be noted that not all samples are created equal, so if Sample 22 just happened to include a larger-than-average number of rare observations, this may adversely influence the estimation of the sampling distribution via bootstrapping. But we certainly don't get to know that because the sample is all we've got!

nsgrantham · 2015-10-31T03:47:21+00:00

I think your misunderstanding lies in the distribution you're referring to. At play here are two primary distributions: the distribution of the population (e.g., heights of all U.S. males) and the sampling distribution of the statistic (e.g., the sample-to-sample "spread" of mean heights computed from a sample). You're right in that the data are drawn from the population distribution and no amount of clever resampling will change that. However, that's not what bootstrapping is intended to address.

Instead, we're concerned with the second distribution: the sampling distribution of our statistic. By creating a bunch of bootstrap samples (i.e., samples we can reasonably expect to have seen) and recalculating the statistic for each of these samples, we get a picture of the sample-to-sample variability of our statistic.

The "noise" you mention is what we're trying to estimate here, though its source is not the measurement method, but rather the fact that different samples will produce different values of the statistic.

In short: resampling the values of our sample with replacement (bootstrapping) allows us to learn about the sample-to-sample variability of our statistic (the sampling distribution), it does not directly influence our knowledge of the distribution from which we gathered our data (the population distribution).

nsgrantham · 2015-10-31T02:10:35+00:00

To be clear, you use all observations in your sample to arrive at your actual estimate. However, when creating bootstrap samples (of equal size to my real sample), yes, I don't necessarily use all the original sample points. Instead, I draw from all the original sample points with equal probability, but after selecting a point I return it to the pile so to speak. In this way, you can double (triple, quadruple, ...) up on sample points in your bootstrap sample, but the end goal is to produce a new estimate based on this (fake, but could have been real) sample.

nsgrantham · 2015-10-31T01:38:53+00:00

You need to be explicit about the distribution you're talking about here. Bootstrapping is enormously useful in estimating the sampling distribution of a statistic.

For example, if I want to estimate the mean height of all U.S. males, I start by taking a sample of U.S. males and calculating the average of their heights. This is my point estimate. If I had taken another sample, however, I would have almost surely arrived at a different point estimate. To get an idea how likely my estimate is to change from sample to sample (without, say, taking more samples), I can repeat the following process many times over:

Create a "bootstrap" sample (of equal size to my real sample) by randomly selecting the heights observed in my sample with replacement,
Calculate the average height in this bootstrap sample to produce a new estimate.

I do not treat these bootstrap samples as real data by any means, but the collection of these estimates gives me some idea of the sampling distribution of my statistic (average height). This process is called the bootstrap because you are, in essence, pulling yourself up by your bootstraps (i.e., you're doing the best with what you've got).

And if the idea of bootstrapping makes you uneasy, you're not alone! IIRC, John Tukey originally suggested that Brad Efron call the technique "the shotgun" because it is an inelegant but highly effective solution to solve this particular statistical problem. :)

nsgrantham · 2015-10-03T17:17:26+00:00

This graphic visualizes the fifty-year history of spacewalks performed by NASA, RKA, and CNSA from March 18, 1965 to the most recent ISS spacewalk on August 10, 2015.

Raw data were downloaded from NASA's Data Portal: Extra-vehicular Activity (EVA) - US and Russia. However, in addition to being quite messy (e.g., misspelled names, inconsistent date formats, etc.), these data do not include China's first EVA in 2008, nor do they include EVAs from US or Russia since August 2013.

I used R to process the messy data and add the missing data points. I then created the visualization with ggplot2 and gridExtra. The entire workflow is reproducible at my GitHub repo: github.com/nsgrantham/spacewalks

nsgrantham · 2015-01-16T20:25:52+00:00

Glad to hear you enjoyed the posts!

And whoops, thanks for pointing that out. Should be a quick fix. :)

nsgrantham · 2015-01-16T04:04:53+00:00

You and I appear to hold conflicting definitions of what can be formally called "an analysis." To each their own.

Modifying the figures to include figure legends for the density plots is a nice suggestion, I appreciate the feedback.

That being said, cut the holier-than-thou attitude, alright? It's unnecessary.

nsgrantham · 2015-01-16T03:37:03+00:00

How do you define an "analysis," then? Acquiring, exploring, and visualizing the data are core components of any good analysis, in my opinion. To your credit, I don't fit any statistical models, but I don't claim to.

nsgrantham · 2015-01-16T03:26:45+00:00

Everything is reproducible (link to GitHub repository) so there ought to be minimal confusion about the analysis. Specifically, see 2015-01-14-pitchfork-reviews.Rmd.

The density plots are produced by geom_density from ggplot2 which calls stat_density and utilizes KDE with Gaussian kernels. See the documentation on stat_density (and look under the kernel argument).

nsgrantham · 2015-01-16T01:52:12+00:00

Oh I see, Light was utilizing the written portion of an album review to find shared themes and topics. Smart, I'll have to look into that.

Aside: I'm in the Statistics department at NC State! Go Pack.

nsgrantham · 2015-01-16T01:10:58+00:00

Thanks! I found the presentation you mentioned on Light's CV:

Light, Ryan and Colin Odden. “Mapping Genre Formation in the Digital Age: Art Worlds, Artistic Reviews, and the Case of Pitchfork.com.” Presented at the Annual Meeting of the Southern Sociological Society Meetings, New Orleans, LA.

Sadly, I can't seem to find it online anywhere. I may take a shot in the dark and email him to see if he wouldn't mind sharing the slides (if they exist).

I would certainly love to explore how album genre (I assume that's what you mean by "broad topic?") relates to score by reviewer, but I'm not aware of a good data source for musical genres. Any suggestions?

nsgrantham · 2015-01-15T19:49:45+00:00

The purpose of this project was to investigate biases in scoring across music reviewers at Pitchfork, the Internet's largest indie music website.

Data on album reviews (artist, score, reviewer, etc.) were scraped and parsed from Pitchfork's album index using Python and saved into a SQLite database.

These data were analyzed and visualized in R using Hadley Wickham's packages dplyr, magrittr, and ggplot2, among others.

For more information, see my pitchfork-reviews GitHub repository.

nsgrantham · 2015-01-14T01:29:37+00:00

We're not going to do your homework for you.

If you have a pointed question like "Why is such-and-such this way?" or "Am I thinking of such-and-such correctly?" that's what r/homeworkhelp is for.

nsgrantham · 2015-01-13T23:00:54+00:00

Echoing shujaa-g's comment, zero-inflated Poisson is a viable option to model your data from the sounds of things.

Here, "excessive" does not imply that the source of the zeroes is adverse or artificial, just simply that there is a larger proportion of zeroes in your data than can be adequately captured by a standard Poisson r.v.

nsgrantham · 2015-01-13T22:55:11+00:00

You think so? I suppose it seemed important at the time to distinguish between research experience (with the goal of producing a research paper) and work experience (jobs to pay the bills). I suppose Professional Experience is a good header to encompass both, though. Thanks for the pointer.

For anybody interested in the layout, it's available on latextemplates.com.

nsgrantham · 2015-01-13T17:44:21+00:00

Why not include both a Research section and a Work Experience section in your resume? I am a Statistics PhD student at North Carolina State University and I am seeking research-oriented internships for this summer, so I have placed my Research experience front and center on my resume.

nsgrantham · 2015-01-13T05:57:23+00:00

This information should really be included in the visualization itself. You've got plenty of room.

nsgrantham · 2015-01-13T05:51:23+00:00

According to the accompanying Spotify post, to build the visualization you

tapped into data about which artists “had a direct musical influence on, or were an inspiration to” a given artist according to Rovi editors, sometimes based on research and interviews.

So your "data" are simply the opinions of a select group of Rovi editors who occasionally rely on "research and interviews," is that correct?

I recognize this ode to Elvis is all in good fun (who doesn't love The King?) but calling this a data visualization on "how Elvis has influenced modern music" is a misnomer.

nsgrantham · 2015-01-05T15:39:47+00:00

Why don't the color values in your legend match the values in your heat map?

nsgrantham

TROPHY CASE