decision-tree | Decision tree on Golang | Rule Engine library

The issue is quite subtle. To make your reference work you have to add a line break after the code chunk and the following text:

To listen to change events on your select element you can observe changes like so:

Many matplotlib functions follow the color cycler to assign default colors, but that doesn't seem to apply here.

The following approach loops through the generated annotation texts (artists) and the clf tree structure to assign colors depending on the majority class and the impurity (gini). Note that we can't use alpha, as a transparent background would show parts of arrows that are usually hidden.

You could try like this:

Decision Tree can work without Standard Scaler and with Standard Scaler. The important thing to note here is that scaling the data won't affect the performance of a Decision Tree model.

If you are plotting the data afterwards though I imagine you don't want to plot the scaled data but rather the original data; hence your problem.

The simplest solution I can think of for doing this is to pass sparse=True as an argument to numpy.meshgrid as that seems to be what's throwing the error in your traceback. There's some detail on that in a past question here.

So applied to your question, that would mean you change this line:

You have a problem with your y labels. If your model should predict if a sample belong to class A or B you should, according to your dataset, use the index as label y as follow since it contains the class ['A', 'B']:

You cannot use the export_text function on the whole pipeline as it only accepts Decision Tree objects, i.e. DecisionTreeClassifier or DecisionTreeRegressor. Only pass the fitted estimator of your pipeline and it will work:

Answer

ctree only creates splits if those reach statistical significance (see ?ctree for the underlying tests). In your case, none of the splits do so, and therefore no splits are provided.

In your case, you could force a full tree by messing with the controls (see ?ctree and ?ctree_control), e.g. like this:

Would it be SEO friendly since the heading would come from the logo's alternative text?

Should be fine. However as you will see there is a better way to structure this that will be better for SEO.

Would it be better to put a aria-label="Company" and title="Company" within the link so the heading comes from there?

No it will be more compatible the way you have it now. Don't use title it is useless for accessibility and nowadays more devices are touch based than pointer based so it doesn't serve much purpose there either.

Or is this approach just not acceptable at all and I should use something else as the H1?

The approach is acceptable (adding a hyperlink to a

) but your current implementation is not acceptable.

The

should describe the page you are currently on so that an end user knows they are in the correct place.

Your alt attribute describes the logo, which is correct for the home page link but not useful to describe the page. (If a screen reader user uses shortcuts to read the page

they will hear "Link, Company homepage". This would be confusing.)

Also the other issue with this is that the company logo is nearly always used as a shortcut for "home", so you either end up breaking that convention on other pages (as you can't have a hyperlink saying "about us" that leads to the home page) or break convention be having the logo point to the current page.

Neither of these are a good idea.

So what are my options?

Obviously as you stated a visual heading on the page would be best. This isn't just for users of assistive tech but also useful for everybody to help orientate them on the site. If you can make this work the advice is to do that. This is 10 times more effective than the next option.

However assuming you cannot make a visible

work on the page the next best thing would be a that is hidden using visually hidden text.

This means that screen reader users can still access the

without it changing the visual design. It also means you can leave the logo link to the homepage as it should be, in line with conventions and expected behaviour.

Also because of the issues mentioned previously this should be separate and in a logical place in the document, such as the beginning of the element.

Example