# 8.6E: Exercises

## Exercise (PageIndex{1})

Use the ratio test to determine whether (displaystyle sum^∞_{n=1}a_n) converges, where (displaystyle a_n) is given in the following problems. State if the ratio test is inconclusive.

1) (displaystyle a_n=1/n!)

Solution: (displaystyle a_{n+1}/a_n→0.) Converges.

2) (displaystyle a_n=10^n/n!)

3) (displaystyle a_n=n^2/2^n)

Solution: (displaystyle frac{a_{n+1}}{a_n}=frac{1}{2}(frac{n+1}{n})^2→1/2<1.) Converges.Add texts here. Do not delete this text first.

4) (displaystyle a_n=n^{10}/2^n)

5) (displaystyle sum_{n=1}^∞frac{(n!)^3}{(3n!)})

Solution: (displaystyle frac{a_{n+1}}{a_n}→1/27<1.) Converges.

6) (displaystyle sum_{n=1}^∞frac{2^{3n}(n!)^3}{(3n!)})

7) (displaystyle sum_{n=1}^∞frac{(2n)!}{n^{2n}})

Solution: (displaystyle frac{a_{n+1}}{a_n}→4/e^2<1.) Converges.

8) (displaystyle sum_{n=1}^∞frac{(2n)!}{(2n)^n})

9) (displaystyle sum_{n=1}^∞frac{n!}{(n/e)^n})

Solution: (displaystyle frac{a_{n+1}}{a_n}→1.) Ratio test is inconclusive.

10) (displaystyle sum_{n=1}^∞frac{(2n)!}{(n/e)^{2n}})

11) (displaystyle sum_{n=1}^∞frac{(2^nn!)^2}{(2n)^{2n}})

Solution: (displaystyle frac{a_n}{a_{n+1}}→1/e^2.) Converges.

## Exercise (PageIndex{2})

Use the root test to determine whether (displaystyle sum^∞_{n=1}a_n) converges, where (displaystyle a_n) is as follows.

1) (displaystyle a_k=(frac{k−1}{2k+3})^k)

2) (displaystyle a_k=frac{(2k^2−1}{k^2+3})^k)

Solution: (displaystyle (a_k)^{1/k}→2>1.) Diverges.

3) (displaystyle a_n=frac{(lnn)^{2n}}{n^n})

4) (displaystyle a_n=n/2^n)

Solution: (displaystyle (a_n)^{1/n}→1/2<1.) Converges

5) (displaystyle a_n=n/e^n)

6) (displaystyle a_k=frac{k^e}{e^k})

Solution: (displaystyle (a_k)^{1/k}→1/e<1.) Converges.

7) (displaystyle a_k=frac{π^k}{k^π})

8) (displaystyle a_n=(frac{1}{e}+frac{1}{n})^n)

Solution: (displaystyle a^{1/n}_n=frac{1}{e}+frac{1}{n}→frac{1}{e}<1.) Converges.

9) (displaystyle a_k=frac{1}{(1+lnk)^k})

10) (displaystyle a_n=frac{(ln(1+lnn))^n}{(lnn)^n})

Solution: (displaystyle a^{1/n}_n=frac{(ln(1+lnn))}{(lnn)}→0) by L’Hôpital’s rule. Converges.

## Exercise (PageIndex{3})

In the following exercises, use either the ratio test or the root test as appropriate to determine whether the series (displaystyle sum_{k=1}^∞a_k) with given terms (displaystyle a_k) converges, or state if the test is inconclusive.

1) (displaystyle a_k=frac{k!}{1⋅3⋅5⋯(2k−1)})

2) (displaystyle a_k=frac{2⋅4⋅6⋯2k}{(2k)!})

Solution: (displaystyle frac{a_{k+1}}{a_k}=frac{1}{2k+1}→0.) Converges by ratio test

3) (displaystyle a_k=frac{1⋅4⋅7⋯(3k−2)}{3^kk!})

4) (displaystyle a)n=(1−frac{1}{n})^{n^2})

Solution: (displaystyle (a_n)^{1/n}→1/e.) Converges by root test.

5) (displaystyle a_k=(frac{1}{k+1}+frac{1}{k+2}+⋯+frac{1}{2k})^k) (Hint: Compare (displaystyle a^{1/k}_k) to (displaystyle ∫^{2k}_kfrac{dt}{t}).)

6) (displaystyle a_k=(frac{1}{k+1}+frac{1}{k+2}+⋯+frac{1}{3k})^k)

Solution: (displaystyle a^{1/k}_k→ln(3)>1.) Diverges by root test.

7) (displaystyle a_n=(n^{1/n}−1)^n)

## Exercise (PageIndex{4})

Use the ratio test to determine whether (displaystyle sum_{n=1}^∞a_n) converges, or state if the ratio test is inconclusive.

1) (displaystyle sum_{n=1}^∞frac{3^{n^2}}{2^{n^3}})

Solution: (displaystyle frac{a_{n+1}}{a_n}= frac{3^{2n+1}}{2^{3n^2+3n+1}}→0.) Converge.

2) (displaystyle sum_{n=1}^∞frac{2^{n^2}}{n^nn!})

## Exercise (PageIndex{5})

Use the root and limit comparison tests to determine whether (displaystyle sum_{n=1}^∞a_n) converges.

1) (displaystyle a_n=1/x^n_n) where (displaystyle x_{n+1}=frac{1}{2}x_n+frac{1}{x_n}, x_1=1) (Hint: Find limit of (displaystyle {x_n}).)

Solution: Converges by root test and limit comparison test since (displaystyle x_n→sqrt{2}).

## Exercise (PageIndex{6})

In the following exercises, use an appropriate test to determine whether the series converges.

1) (displaystyle sum_{n=1}^∞frac{(n+1)}{n^3+n^2+n+1})

2) (displaystyle sum_{n=1}^∞frac{(−1)^{n+1}(n+1)}{n^3+3n^2+3n+1})

Solution: Converges absolutely by limit comparison with p−series, (displaystyle p=2.

3) (displaystyle sum_{n=1}^∞frac{(n+1)^2}{n^3+(1.1)^n})

4) (displaystyle sum_{n=1}^∞frac{(n−1)^n}{(n+1)^n})

Solution: (displaystyle lim_{n→∞}a_n=1/e^2≠0). Series diverges.

5) (displaystyle a_n=(1+frac{1}{n^2})^n) (Hint: (displaystyle (1+frac{1}{n^2})^{n^2}≈e.))

6) (displaystyle a_k=1/2^{sin^2k})

Solution: Terms do not tend to zero: (displaystyle a_k≥1/2,) since (displaystyle sin^2x≤1.

7) (displaystyle a_k=2^{−sin(1/k)})

8) (displaystyle a_n=1/(^{n+2}_n)) where (displaystyle (^n_k)=frac{n!}{k!(n−k)!})

Solution: (displaystyle a_n=frac{2}{(n+1)(n+2)},) which converges by comparison with p−series for (displaystyle p=2)

9) (displaystyle a_k=1/(^{2k}_k))

10) (displaystyle a_k=2^k/(^{3k}_k))

Solution: (displaystyle a_k=frac{2^k1⋅2⋯k}{(2k+1)(2k+2)⋯3k}≤(2/3)^k) converges by comparison with geometric series

11) (displaystyle a_k=(frac{k}{k+lnk})^k) (Hint: (displaystyle a_k=(1+frac{lnk}{k})^{−(k/lnk)lnk}≈e^{−lnk}).)

12) (displaystyle a_k=(frac{k}{k+lnk})^{2k}) (Hint: (displaystyle a_k=(1+frac{lnk}{k})^{−(k/lnk)lnk^2}.))

Solution: (displaystyle a_k≈e^{−lnk^2}=1/k^2.) Series converges by limit comparison with (displaystyle p−series, p=2.)

## Exercise (PageIndex{7})

The following series converge by the ratio test. Use summation by parts, (displaystyle sum_{k=1}^na_k(b_{k+1}−b_k)=[a_{n+1}b_{n+1}−a_1b_1]−sum_{k=1}^nb_{k+1}(a_{k+1}−a_k),) to find the sum of the given series.

1) (displaystyle sum_{k=1}^∞frac{k}{2^k}) (Hint: Take (displaystyle a_k=k) and (displaystyle b_k=2^{1−k}).)

2) (displaystyle sum_{k=1}^∞frac{k}{c^k},) where (displaystyle c>1) (Hint: Take (displaystyle a_k=k) and (displaystyle b_k=c^{1−k}/(c−1)).)

Solution: If (displaystyle b_k=c^{1−k}/(c−1)) and (displaystyle a_k=k), then (displaystyle b_{k+1}−b_k=−c^{−k}) and (displaystyle sum_{n=1}^∞frac{k}{c^k}=a_1b_1+frac{1}{c−1}sum_{k=1}^∞c^{−k}=frac{c}{(c−1)^2}.)

3) (displaystyle sum_{n=1}^∞frac{n^2}{2^n})

4) (displaystyle sum_{n=1}^∞frac{(n+1)^2}{2^n})

Solution: (displaystyle 6+4+1=11)

## Exercise (PageIndex{8})

The kth term of each of the following series has a factor (displaystyle x^k). Find the range of (displaystyle x) for which the ratio test implies that the series converges.

1) (displaystyle sum_{k=1}^∞frac{x^k}{k^2})

2) (displaystyle sum_{k=1}^∞frac{x^{2k}}{k^2})

Solution: (displaystyle |x|≤1)

3) (displaystyle sum_{k=1}^∞frac{x^{2k}}{3^k})

4) (displaystyle sum_{k=1}^∞frac{x^k}{k!})

Solution: (displaystyle |x|<∞

5) Does there exist a number (displaystyle p) such that (displaystyle sum_{n=1}^∞frac{2^n}{n^p}) converges?

6) Let (displaystyle 0

Solution: All real numbers (displaystyle p) by the ratio test.

7) Suppose that (displaystyle lim_{n→∞}∣frac{a_{n+1}}{a_n}∣=p.) For which values of (displaystyle p) must (displaystyle sum_{n=1}^∞2^na_n) converge?

8) Suppose that (displaystyle lim_{n→∞}∣frac{a_{n+1}}{a_n}∣=p.) For which values of (displaystyle r>0) is (displaystyle sum_{n=1}^∞r^na_n) guaranteed to converge?

Solution: (displaystyle r<1/p)

9) Suppose that (displaystyle ∣frac{a_{n+1}}{a_n}∣ ≤(n+1)^p) for all (displaystyle n=1,2,…) where (displaystyle p) is a fixed real number. For which values of (displaystyle p) is (displaystyle sum_{n=1}^∞n!a_n) guaranteed to converge?

10) For which values of (displaystyle r>0), if any, does (displaystyle sum_{n=1}^∞r^{sqrt{n}}) converge? (Hint: (displaystyle sum_{n=1}^∞a_n=sum_{k=1}^∞sum_{n=k^2}^{(k+1)^2−1}a_n.))

Solution: (displaystyle 0

11) Suppose that (displaystyle ∣frac{a_{n+2}}{a_n}∣ ≤r<1) for all (displaystyle n). Can you conclude that (displaystyle sum_{n=1}^∞a_n) converges?

12) Let (displaystyle a_n=2^{−[n/2]}) where (displaystyle [x]) is the greatest integer less than or equal to x. Determine whether (displaystyle sum_{n=1}^∞a_n) converges and justify your answer.

Solution: One has (displaystyle a_1=1, a_2=a_3=1/2,…a_{2n}=a_{2n+1}=1/2^n). The ratio test does not apply because (displaystyle a_{n+1}/a_n=1) if (displaystyle n) is even. However, (displaystyle a_{n+2}/a_n=1/2,) so the series converges according to the previous exercise. Of course, the series is just a duplicated geometric series.

## Exercise (PageIndex{9})

The following advanced exercises use a generalized ratio test to determine convergence of some series that arise in particular applications when tests in this chapter, including the ratio and root test, are not powerful enough to determine their convergence. The test states that if (displaystyle lim_{n→∞}frac{a_{2n}}{a_n}<1/2), then (displaystyle sum a_n) converges, while if (displaystyle lim_{n→∞}frac{a_{2n+1}}{a_n}>1/2), then (displaystyle sum a_n) diverges.

1) Let (displaystyle a_n=frac{1}{4}frac{3}{6}frac{5}{8}⋯frac{2n−1}{2n+2}=frac{1⋅3⋅5⋯(2n−1)}{2^n(n+1)!}). Explain why the ratio test cannot determine convergence of (displaystyle sum_{n=1}^∞a_n). Use the fact that (displaystyle 1−1/(4k)) is increasing (displaystyle k) to estimate (displaystyle lim_{n→∞}frac{a_{2n}}{a_n}).

2) Let (displaystyle a_n=frac{1}{1+x}frac{2}{2+x}⋯frac{n}{n+x}frac{1}{n}=frac{(n−1)!}{(1+x)(2+x)⋯(n+x).}) Show that (displaystyle a_{2n}/a_n≤e^{−x/2}/2). For which (displaystyle x>0) does the generalized ratio test imply convergence of (displaystyle sum_{n=1}^∞a_n)? (Hint: Write (displaystyle 2a_{2n}/a_n) as a product of (displaystyle n) factors each smaller than (displaystyle 1/(1+x/(2n)).))

Solution: (displaystyle a_{2n}/a_n=frac{1}{2}⋅frac{n+1}{n+1+x}frac{n+2}{n+2+x}⋯frac{2n}{2n+x}.) The inverse of the (displaystyle kth) factor is (displaystyle (n+k+x)/(n+k)>1+x/(2n)) so the product is less than (displaystyle (1+x/(2n))^{−n}≈e^{−x/2}.) Thus for (displaystyle x>0, frac{a_{2n}}{a_n}≤frac{1}{2}e^{−x/2}). The series converges for (displaystyle x>0).

3) Let (displaystyle a_n=frac{n^{lnn}}{(lnn)^n}.) Show that (displaystyle frac{a_{2n}}{a_n}→0) as (displaystyle n→∞.)

## 8.6F: Sodium

• Contributed by The University of Hawaiʻi
• Human Nutrition at University of Hawai&rsquoi at Mānoa

Sodium is vital not only for maintaining fluid balance but also for many other essential body functions. In contrast to many minerals, sodium absorption in the small intestine is extremely efficient and in a healthy individual, all excess sodium is excreted by the kidneys. In fact, very little sodium is required in the diet (about 200 milligrams) because the kidneys actively reabsorb sodium. Kidney reabsorption of sodium is hormonally controlled, allowing for a relatively constant sodium concentration in the blood.

The typical American diet today is quite high in sodium, often providing > 2,300 milligrams of sodium per day. This is especially true if a person eats a lot of processed or packaged foods. For young people with healthy kidneys excess sodium intake may not be a problem. However, high sodium intake can have serious consequences for people with compromised kidney function. In addition, during the normal aging process the kidneys often become less efficient at excreting excess sodium from the blood. In either case, the result of compromised kidney function is the retention of fluid in the blood leading to higher pressure within the blood vessels. This condition is know as high blood pressure or hypertension, and can often be controlled by reducing the amount of sodium consumed.

## 8.2 Logistic Regression

The best known of the GLM class of models is the logistic regression that deals with Binomial, or more precisely, Bernoulli-distributed data. The link function in the logistic regression is the logit function [egin g(t)=logleft( frac <(1-t)> ight) ag <8.2>end] implying that under the logistic model assumptions [egin y|x sim Binom left( 1, p=frac<>><1+e^> ight). ag <8.3>end]

Before we fit such a model, we try to justify this construction, in particular, the enigmatic link function in Eq.(8.2). Let’s look at the simplest possible case: the comparison of two groups indexed by (x) : (x=0) for the first, and (x=1) for the second. We start with some definitions.

Odds are the same as probabilities, but instead of telling me there is a (66\%) of success, they tell me the odds of success are “2 to 1”. If you ever placed a bet, the language of “odds” should not be unfamiliar to you.

Odds ratios (OR) compare between the probabilities of two groups, only that it does not compare them in probability scale, but rather in odds scale. You can also think of ORs as a measure of distance between two Brenoulli distributions. ORs have better mathematical properties than other candidate distance measures, such as (P(y_1=1)-P(y_2=1)) .

Under the logit link assumption formalized in Eq.(8.3), the OR between two conditions indexed by (y|x=1) and (y|x=0) , returns: [egin OR(y|x=1,y|x=0) = frac = e^<eta_1>. end]

The last equality demystifies the choice of the link function in the logistic regression: it allows us to interpret (eta) of the logistic regression as a measure of change of binary random variables, namely, as the (log) odds-ratios due to a unit increase in (x) .

### 8.2.1 Logistic Regression with R

Let’s get us some data. The PlantGrowth data records the weight of plants under three conditions: control, treatment1, and treatment2.

We will now attach the data so that its contents is available in the workspace (don’t forget to detach afterwards, or you can expect some conflicting object names). We will also use the cut function to create a binary response variable for Light, and Heavy plants (we are doing logistic regression, so we need a two-class response). As a general rule of thumb, when we discretize continuous variables, we lose information. For pedagogical reasons, however, we will proceed with this bad practice.

Look at the following output and think: how many group effects do we expect? What should be the sign of each effect?

Let’s fit a logistic regression, and inspect the output.

The glm function is our workhorse for all GLM models.

The family argument of glm tells R the respose variable is brenoulli, thus, performing a logistic regression.

The summary function is content aware. It gives a different output for glm class objects than for other objects, such as the lm we saw in Chapter 7. In fact, what summary does is merely call summary.glm .

As usual, we get the coefficients table, but recall that they are to be interpreted as (log) odd-ratios, i.e., in “link scale”. To return to probabilities (“response scale”), we will need to undo the logistic transformation.

As usual, we get the significance for the test of no-effect, versus a two-sided alternative. P-values are asymptotic, thus, only approximate (and can be very bad approximations in small samples).

The residuals of glm are slightly different than the lm residuals, and called Deviance Residuals.

AIC (Akaike Information Criteria) is the equivalent of R2 in logistic regression. It measures the fit when a penalty is applied to the number of parameters (see AIC definition here). Smaller AIC values indicate the model is closer to the truth.

Null deviance: Fits the model only with the intercept. The degree of freedom is n-1. We can interpret it as a Chi-square value (fitted value different from the actual value hypothesis testing).

Residual Deviance: Model with all the variables. It is also interpreted as a Chi-square hypothesis testing.

Number of Fisher Scoring iterations: Number of iterations before converging ().

For help see ?glm , ?family , and ?summary.glm .

Like in the linear models, we can use an ANOVA table to check if treatments have any effect, and not one treatment at a time. In the case of GLMs, this is called an analysis of deviance table.

• The anova function, like the summary function, are content-aware and produce a different output for the glm class than for the lm class. All that anova does is call anova.glm .
• In GLMs there is no canonical test (like the F test for lm ). LRT implies we want an approximate Likelihood Ratio Test. We thus specify the type of test desired with the test argument.
• The distribution of the weights of the plants does vary with the treatment given, as we may see from the significance of the group factor.
• Readers familiar with ANOVA tables, should know that we computed the GLM equivalent of a type I sum- of-squares. Run drop1(glm.1, test='Chisq') for a GLM equivalent of a type III sum-of-squares.
• For help see ?anova.glm .

Let’s predict the probability of a heavy plant for each treatment.

• Like the summary and anova functions, the predict function is aware that its input is of glm class. All that predict does is call predict.glm .
• In GLMs there are many types of predictions. The type argument controls which type is returned. Use type=response for predictions in probability scale use type=link’ for predictions in log-odds scale.
• How do I know we are predicting the probability of a heavy plant, and not a light plant? Just run contrasts(weight.factor) to see which of the categories of the factor weight.factor is encoded as 1, and which as 0.
• For help see ?predict.glm .

Let’s detach the data so it is no longer in our workspace, and object names do not collide.

We gave an example with a factorial (i.e. discrete) predictor. We can do the same with multiple continuous predictors.

### 8.2.2 Another Logistic regression example and model evaluation

Let’s model the relationship between the probability that an iris flower is of type “setosa”, and the length of its Sepal.

Again, we do logistic regression. Let’s check the fitted probabilities:

If we are interested in a prediction whether a flower is “setosa” or not, we need a decision rule. A trivial rule is: classify as “1” (’is_setosa=1) if (hat

( ext=1| ext)>0.5)

We can plot the data and distinguish between samples we classed to 1 and 0. We also add the predicted probabilities and the 0.5 threshold:

Note that other thresholds are also possible (this is a question of False positives and false negatives)

Let’s compare a logistic and a linear models in a prediction problem. We use the spam dataset from the ElemStatLearn package (see ?ElemStatLearn::spam ):

## Compliance with the disclosure requirements, transparency rules and corporate governance rules1

A listed company, whose equity shares5 are admitted to trading on a regulated market15, should consider the obligations under the disclosure requirements12.

A listed company that is not already required to comply with the obligations referred to under article 17 of the Market Abuse Regulation12 must comply with those obligations12 as if it were an issuer for the purposes of the disclosure requirements12 and transparency rules subject to article 22 of the Market Abuse Regulation12.

1A listed company, whose equity shares5are admitted to trading on a regulated market, should consider its obligations under DTR 4 (Periodic financial reporting), DTR 5 (Vote holder and issuer notification rules),4 DTR 6 (Access to information) and DTR 7 (Corporate governance).4

1A listed company that is not already required to comply with the transparency rules15must comply with DTR 4 , DTR 5 and DTR 6 as if it were an issuer for the purposes of the transparency rules.

16A listed company that is not already required to comply with DTR 7.3 (Related party transactions)19 must comply with DTR 7.3 as if it were an issuer to which DTR 7.3 applies, subject to the modifications set out in LR 9.2.6DR .

16For the purposes of LR 9.2.6CR , DTR 7.3 is modified as follows:

DTR 7.3.2R must be read as if the words “has the meaning in UK-adopted IFRS19” are replaced by:

where the listed company prepares annual consolidated financial statements in accordance with accounting standards which have been determined to be equivalent to UK-adopted IFRS and which are set out in the TD Equivalence Decision19,

in the equivalent accounting standards in accordance with which its annual consolidated financial statements are prepared

as if the words “after obtaining board approval” are replaced by “after publishing an announcement in accordance with DTR 7.3.8R(1) ” and

the reference to DTR 7.3.8R must be read as a reference to DTR 7.3.8R as modified by LR 9.2.6DR(2) and

in DTR 7.3.13R the references to DTR 7.3.8R must be read as references to DTR 7.3.8R as modified by LR 9.2.6DR(2) .

## Product Description

KMP 8x6E 8*6E High Efficiency Propeller 1 Pcs

Description:
Brand Name: KMP
Item Name: 8x6E propeller

Features:
High quality and high speed propeller.
Solid material and precise curved surface,
Good workmanship,can keep the blade not deformed in high speed rotation,maintaining the highest efficiency.

Package Included:
1x KMP 8x6E propeller

• 10 MM Drop
• Blown Rubber Outsole
• Dual Density Collar Foam
• HCPCS Code A5500
• Molded Insole
• Removable insole
• A Bit Of Stretch For Easier On/Off
• Breathable Mesh
• 24% lighter
• ENCAP Soft Cushioning Midsole
• ROLLBAR Designed To Reduce Rear Foot Movement
• Weight: 423 grams (14.9 oz)

### Foot Conditions*

* Based on the Features, this product may be appropriate for the listed Foot Conditions.

The information provided by Healthy Feet Store, LLC and Dr. Hurless is intended for educational purposes only and not intended to be used as a recommendation for a patient's specific medical condition, treatment plan or management of a disease. Please consult your healthcare provider.

## 1.1 Simulate the data

Prior to generating the data we set the seed so that we get similar results. To then generate values for a pure random walk, rw , we just sum a sequency of white noise errors (i.e. the effects of shocks do not dissipate). The time trend, trd , is a sequence of observations than spans from 1 to 500 and the random walk with drift includes the realisations for the random walk and the deterministic time trend. The trend stationary process, dt , includes just the deterministic trend and noise and an ar1 process with a coefficient of 0.8 is simulated with the aid of the arima.sim command.

To ensure that these calculations have been performed correctly, we could inspect the data with the plot.ts command.

## The FCA technical note

The FCA has also issued a Technical Note, entitled "Disclosures in relation to environmental, social and governance issues (ESG) matters, including climate change", to clarify its expectations in relation to existing FCA rules in this area. The FCA notes that the Technical Note applies with immediate effect and impacts a wider scope of companies than the new listing rule. It is relevant, broadly, to all listed companies and those companies subject to the Market Abuse Regulation (MAR) and Prospectus Regulation (PR).

Briefly, the Technical Note looks at the Listing Rules, the Disclosure Guidance and Transparency Rules (DTRs), the PR and MAR and lists existing obligations that may require disclosure of ESG matters. In some cases, it offers non-exhaustive explanations and/or examples of how these rules might apply in respect of ESG issues.

For example, the FCA notes Listing Principle 1 on adequate procedures, systems and controls to enable a company to comply with its obligations. It states that listed companies should consider whether they need to access and draw on specific data sources (that may not typically be used for general business purposes) when disclosing climate-related and other ESG-related risks and opportunities, and whether there is a need to develop specific, possibly bespoke, systems, analytical instruments or organisational arrangements to collate and assess information.

In a further example, looking at the DTRs which require disclosures amounting to a fair review of the business and a description of the principal risks and uncertainties, the FCA says that, in the context of the Government's target to achieve net-zero carbon emissions by 2050 and to achieve the goals of the Paris Agreement more generally, many companies are likely to need to consider significant changes to their business. These changes may be material to an investor's assessment of the prospects of the company and the risks and opportunities shaping it.

In PS 20/17, the FCA notes the variety of further guidance that people requested be covered in the Technical Note in their replies to the consultation. These are perhaps a good illustration of the areas respondents are somewhat troubled by. For example, there were requests for guidance/discussion on determining the materiality of ESG matters for disclosure and on what types of ESG matters amounted to inside information. On the whole the FCA has left the Technical Note unchanged from the consultation version and whilst it acknowledged difficulties in some of the areas, did not feel it appropriate to go into these and other matters in the Technical Note.

## 22 thoughts on &ldquo Comments &rdquo

Item #17 – I agree with making a distinction between uniformity and consistency.

Item #18, a – While the question posed in 18a might be important to political leaders, this question should not be included in this document. It should be deleted.

Item #58, a&b – Delete the word “possibly” in the parentheses. It will definitely be necessary to show separate urban and rural intersections.

Item #95, b, iii – Change to “Although it might be assumed that the NCUTCD process for evaluating rulemaking should be changed to accommodate modern communication methods, it has been found that without the opportunity for face-to-face discussion, it is difficult to effectively review a large number of proposed changes.”

Item #513 – I strongly agree with this statement.

Item #521 – I strongly agree with this statement.

Item #527 – Since this item proposes specific MUTCD text and because some of the items 516 to 525 include subsections, not all of which are deemed appropriate for MUTCD inclusion, this item should state clearly what text should be included under Section 1A.XX MUTCD Guiding Rules:
Section 1A.XX MUTCD Guiding Rules
MUTCD content should comply with the following guiding rules:
MUTCD content should be consistent with the purpose of the MUTCD.
MUTCD content should establish the appropriate level of mandate for a given traffic control device principle.
MUTCD content should be prepared so that it is useable by the intended MUTCD user
and the level of mandate for the content.
MUTCD content and changes to MUTCD content should be based on one or more of
the following:
a. Widespread national experience that conclusively demonstrates the traffic control
device is effective.
b. Peer-reviewed and published research that demonstrates the traffic control device
is effective.
c. A change in federal law or regulation related to traffic control devices.
MUTCD content should not describe traffic engineering practices or other topics that
are not traffic control device activities.
MUTCD content should caution against over-control of the road user.
The MUTCD should not serve as an educational document.
While tort liability is often a traffic control device concern, it should not be a motivating factor in making decisions related to any traffic control device activity.
The MUTCD should provide a means of accommodating advancements in traffic
control device technologies and other traffic control device-related improvements in a
timely manner but in a way that does not rush implementation of new technologies
before they have been fully evaluated.
MUTCD content should recognize that alternative traffic control device treatments or
combinations of treatments may be as or more effective than the treatment specified in
the MUTCD. MUTCD content should allow alternative treatments if there is adequate
justification or evidence of equal or better performance as long as the alternative
treatments do not compromise the uniform standards in the MUTCD.

Item #533 – Since this item proposes specific MUTCD text, delete “The following heading definitions should be added to the MUTCD (see item 536 for a detailed description of each term):”

Item #533, a&b – I agree with the concept of defining a Uniform Standard and a Consistent Standard. The NCUTCD will need to revisit each existing Standard in the MUTCD to identify which will be modified to a Consistent Standard by changing “shall” to “must.”

Item #534 – This item is repetitious of Item #527, and it should be deleted.

Item #537 – I don’t necessarily disagree with this item, but the concern covered in “a” could be handled by implementing realistic compliance dates, and the concern covered in “b” should not be necessary if the provisions listed in Item # 519 are followed.

Item #539 – This item is worded more as a Strategic Plan statement than a Vision statement. The Vision statement should be: “ Rulemaking should only apply to Uniform Standards, Consistent Standards, and Guidance. Option, Preference, and Support statements should not proceed through rulemaking, but should be reviewed and approved through the NCUTCD process.”

The sentence on lines 18 and 19 on page 43 should be deleted. We should affirmatively state that the MUTCD should be restructured, as in Item #540, not qualify it.

Item #541, d – Delete all of d. While the majority of Volume I might be Uniform Standards, I would not recommend that this explicit statement be included in the Vision. Wherever Uniform Standards appear, their definition will apply regarding the ability to revise or modify them.

Item #541, e&f – Delete as unnecessary since Item #539 has already stated what needs to go through rulemaking.

Item #546, a – Add to the end of this statement, “with no more than 25 items covering material that was not previously approved as a recommendation from the NCUTCD.”

Material previously reviewed and approved by the NCUTCD would not need to be reviewed again. The degree to which the relatively short time available in one NCUTCD meeting would compromise the effectiveness of the NCUTCD review would depend on how much new material needed to be reviewed.

Item #546, b – Change this statement to, “Extend the docket comment period for NPA rulemaking that has more than 100 items or more than 25 items covering material that was not previously approved as a recommendation from the NCUTCD to encompass at least two NCUTCD meetings and publish the NPA no less than one month before a NCUTCD meeting.”

Item #546, c – I strongly agree with this statement.

Item #548 – I strongly agree with this statement.

Item #552 – Add to the beginning of the first sentence, “Except as noted in #553,…”

Item #807 – Change “2018” to “2016” in this and all the following items to comply with the decision of FHWA to publish a 2016 MUTCD.

Item #809 – Change this item to the following to comply with the intent of FHWA to publish this material in the 2016 MUTCD:
809. Changes introduced in the 2016 edition should be limited to:
a. Incorporation of all NCUTCD recommendations submitted to FHWA since the last material included in the 2009 MUTCD.
b. Incorporation of all NCUTCD recommendations which can be submitted to FHWA before the NPA is published (probably the June 2014 meeting will be the last NCUTCD meeting before the NPA is published)
c. Content to address new technologies or treatments that have been introduced or developed since the 2009 MUTCD.
d. Possible reorganizations of all Parts of the MUTCD prepared by FHWA staff, but without removing existing text or adding new text that was not previously submitted by the NCUTCD.

Item #814 – Change “Chapter 2” to “Chapter 3”

MUTCD Consultant Services comments on SVP
Abbreviations
Pg vi Add the following Abbreviations:
1. (Access Board) U.S. Architectural and Transportation Barriers Compliance Board.
2. (PROWAG) Proposed Guidelines for Public Rights-of-Way (this item may be deleted if the majority of the Edit commitee feels that the current rulemaking is enough to cover this item)
3. (NPRM) Notice of Proposed Rulemaking (Federal Register Notice)
4. (SNPRM) Supplemental notice of proposed rulemaking (Federal Register Notice)
Items 2,3 & 4 are all Federal register notifications to the public for a Federal action that may affect the MUTCD.
Chapter 1 Introduction
Pg 2 after line 4 insert The Department of Justice is the federal agency with responsibility for issuing regulations implementing the requirements of title II of the ADA and for coordinating federal agency compliance activities with respect to those requirements. Title II applies to the programs and activities of state and local governmental entities. The Department of Justice and the Department of Transportation share responsibility for enforcing the requirements of title II of the ADA with respect to the public right of way, including streets, roads, and highways.
After line 14 add a bullet Provide recommendations for an MUTCD that fosters safety and mobility for all road users , including bicyclists, pedestrians ( including pedestrians with disabilities) to the greatest extent practical.
pg 4 line 4 add two bullets
• The Access Board Proposed Guidelines for Public Rights-of-Way Published in the Federal Register on July 26, 2011
• Supplemental Notice of Proposed Rulemaking on Shared Use Paths was published February 13, 2013.
CHAPTER 2: 1 MUTCD OPINIONS, CHALLENGES, NEEDS, AND QUESTIONS

pg 8 item
4f. Maintenance : The Process of monitoring the visibility, crash worthiness acoustical and tactile features of a device and its performance and taking appropriate actions so that it will function in the intended manner throughout the life of the device and be replaced at the end of its useful life.

Explanation Adding another maintenance feature relating to its mechanical guidance and crash worthiness. For example, an attenuator (say a TMA, which are in the MUTCD now) might still look fine, provide a visibility element and to some degree guidance, but due to a previous minor hit or improper installation, will not do its intended job. Another example would be drums with double bases, which are not officially crash worthy and will not perform part of its “intended function”.
c. Traffic control devices placed in railroad right-of-way may appear to be traffic control devices on public roads but might actually be the responsibility of the railroads.

pg 8 item 6b. Insert the word “clarified” A 2006 revision to 23 CFR 655.603 clarified the application of the MUTCD to privately-owned roads open to public travel
item 6d. Insert the phrase ” are not aware of this requirement and” Many private property owners with roads open to public travel are not aware of this requirement and do not have staff or expertise to make traffic control device decisions.

pg 9 add item 8b.xi Active warning to pedestrians with disabilities that vehicles are in conflict with the pedestrian crossing.
pg 10 Item 17 a. Insert the phrase (including acoustical and tactile ) A specific traffic control device needs to have an identical meaning and general appearance (including acoustical and tactile ) regardless of where it is used. There can be no deviation from requirements related to meaning and appearance

A state who writes their own would either do that for two reasons:

1. They have for a very long time and perhaps they do out of tradition or just to be consistent or …

2. They disagree with most of the national text and a total rewrite is necessary for them.

As far as any “significant differences”: we would need to poll those states.

pg 16 item 44 Should be modified as follows. Adding more levels will be confusing to many users of the MUTCD. Many jurisdictions did not like the increase in the number of STANDARDS in the 2009 MUTCD. Therefore reduce the number of STANDARDS by redefining many of the STANDARDS to GUIDANCE and combine the thoughts in items 44 a-thru g as follows:

44. There may be a need to provide more flexibility to the MUTCD content by modifying or redefining the level of mandates.
a. Standard (required) traffic control device provisions that cannot be modified, revised, or exempted under any conditions.
b. Guidance traffic control device provisions that establish a general range of required criteria or that may be modified, revised, or exempted in limited cases, such as at a specific site with conditions where meeting the standard is impossible or impractical. Traffic control device provisions that indicate recommended courses of action, but which can be revised, modified, or exempted for a variety of reasons. Deviations from Guidance provisions can be based on engineering judgment or engineering study.
c. Option traffic control device provisions that indicate allowable deviations from a required or recommended provision. Use of an optional provision does not require the use of engineering judgment or engineering study.
Traffic control device provisions that indicate a desirable course of action, but which carry no requirement, recommendation, or mandate. Deviations from preferred practice can may be based on engineering judgment.
d. Support information that can explain the basis for specific provisions, cite external content that may be of value, or other information that has no level of mandate.

Explanation for recommendation. The current and future MUTCD content/ text could be revised to the above criteria to keep it simple and avoid massive confusion to many users of the MUTCD .
pg 16 insert under needs. after item 46
There is a need for more research to develop devices to assist persons with disabilities to accommodate their safety and mobility to public rights of way.

pg 26 Delete item 93
pg 30. add an item to Challenges
c. Advancements in technology could lead to a tendency to encourage the use of a new traffic control device without proper human factor studies.
CHAPTER 3: 1 RECOMMENDED VISION
pg 35 insert “international” in item 519 a. “Widespread national and/or international experience that conclusively demonstrates the traffic control device is effective.
pg 37 528. Section 1A.XX Target Road Users
528.a. Change as indicated in red below. Strike out unimpaired and replace it with ” licensed to drive ”
a. One target road user group for traffic control devices is an operator of a vehicle. This target user is the reasonable and prudent individual who is alert, attentive, and licensed to drive, that has a basic proficiency in operating a vehicle on a specific facility, that has demonstrated a basic understanding of traffic control devices and traffic laws, and is operating in a legal and lawful manner that is appropriate for the facility and conditions, while demonstrating due care for the current conditions on the roadway.
Explanation There are some drivers that may have a number of conditions that would be considered to be disabling unless they had modifications that enabled them to drive and be licensed to drive, including reduced vision that requires special optical devices, and missing or prosthetic limbs.
The definition just targets the road user who doesn’t need many traffic control devices. This user would know how to stay alert, know the direction he/she is going (color of the stripes), wouldn’t need wrong ways, do not enters, one-ways signs. Would be able to function normally at a traffic signal, i.e. would not need supplemental mast arm signs, and wouldn’t need the conversion to flashing yellow arrow. This driver doesn’t need high retro values or contrasting signs understands to look for pedestrians, therefore doesn’t need any warning devices, etc, etc, etc.
The Sign Committee understands that we don’t design for the “worst” driver under the normal (bell) curve, but we certainly don’t design for this definition (528) either. We believe it is somewhere in the average to slightly below average range of drivers.

pg 38 530. Section 1A.XX Traffic Control Device Activities:
530.b Insert ” acoustical, tactile” Appearance: The process of establishing the general physical characteristics of a specific device as it appears to the road user. These characteristics include color, shape, legend, acoustical, tactile and the relative position and layout of individual elements.
pg 39 533. Insert ” modified ” Section 1A.XX Definitions: The following heading definitions should be modified to the MUTCD

a. Standard. A statement of required, mandatory, or specifically prohibitive practice regarding a traffic control device. The verb “shall” is used. Normally a standard cannot be revised or modified for any reason. Some Standard statements are sometimes modified by Options.
b. Guidance A statement of normally required to provide consistent practice regarding a traffic control device. The verb “should” is used. Deviations from a consistent guidance are allowed when justified by an engineering study. A statement of recommended, but not mandatory, practice in typical situations, with deviations allowed if engineering judgment or engineering study indicates the deviation to be appropriate. The verb “should” is used. Guidance statements are sometimes modified by Options.
d. Option. A statement of practice that is a permissive condition and carries no requirement or recommendation. Option statements sometime contain allowable modifications to a Standard or Guidance statement. The verb “may” is used.
A statement of preferred practice in typical situations that carries no requirement or recommendations. But does have an expectation that there is indeed a preference established, and to continue uniformity, this option may be used to further participate in the development of such uniformity.
Explanation :The definitions of these statements ought to stand out very clearly in the manual, strikingly so. Many users of the MUTCD simply assume the definitions as they negotiate through the text, without ever having read them nor understand fully the true definitions keeping the definitions simple will decrease the misinterpretation and/or misunderstanding.

f. Support. An informational statement that does not convey any degree of mandate, recommendation, authorization, prohibition, or enforceable condition. The verbs “shall,” “should,” and “may” are not used in Support statements.
Basis for recommendation:
Simple definitions are needed so that many users of the MUTCD will not be confused for the levels of mandate that are recommended.

Pg 40-42 Change Item 536. MUTCD content should be structured to provide a range of mandates as described below:
a. Uniform requirements (Standard)
i. These represent requirements that are needed to establish uniformity across the nation as they relate to critical aspects of traffic control devices.
ii. Normally standards are absolute and cannot be violated at any time under any circumstances.
iii. Standards use the operative verb “shall.”
iv. Standards are required for the meaning, acoustical, tactile and appearance aspects of traffic control devices. Uniform standards can also be established for other aspects of traffic control devices.
v. There is little opportunity for the exercise of discretion in the execution of an activity defined by a standard. As such, activities associated with the execution of a standard are ministerial activities.
vi. Some minor deviations from a standard are permitted.
vii. Some Standards may be modified by an option.
b. Consistent requirements (Guidance)
i. These represent requirements that are needed to establish consistency across the nation as they relate to crucial aspects of traffic control devices.
ii. Consistent Guidance define an expected practice that may have a minimum, maximum, or range of criteria.
iii. Consistent Guidance use the operative verb “should.”
iv. Consistent Guidance would most often apply to selected aspects of use and installation, but can be applied to other aspects of traffic control devices.
v. Deviations from a consistent Guidance are discretionary activities and require an engineering study.
c. Recommended practices (Guidance)
i. These represent recommendations that are needed to promote consistency across the nation as they relate to various aspects of traffic control devices that are deemed important but not crucial.
ii. Guidance defines a recommended practice.
iii. Deviations from guidance may be appropriate due to a wide variety of factors.
iv. Guidance uses the operative verb “should.”
v. Guidance would typically apply to all traffic control device aspects except meaning and appearance.
vi. If the action aligns with the recommendation of the guidance, there is no discretion in the use of guidance. As such, activities associated with the execution of guidance are ministerial activities.
vii. Deviations from guidance are discretionary activities and require the conduct of an engineering study or the exercise of engineering judgment.
d. Optional practices (Option)
i. These represent alternatives that may improve the performance of traffic control devices.
ii. Options define an optional practice.
iii. Options use the operative verb “may.”
iv. Options may exercise engineering judgment depending upon the specific language of the option
v. Implementation of an option may be appropriate due to a wide variety of factors.
vi. Options typically apply to all traffic control device aspects except meaning and appearance.
vii. There is no expectation of compliance with (no requirement to use) an option statement. If an option statement is used, there may be standards or guidance associated with the implementation of the option.
viii. The decision to implement an option is a discretionary act that may require the exercise of engineering judgment. Once a decision has been made to implement an option, the conduct of an option action is a ministerial act that does not require a decision
e. Option Preferred practices (Preference)
i. These represent preferences that are desirable to improve the performance of traffic control devices.
ii. Options Preference defines a desired practice.
iii. Deviations from Options preference may be appropriate due to a wide variety of factors.
iv. Options Preference could typically apply to all traffic control device aspects except meaning and appearance.
vi. There is no expectation of compliance with a Options preferred practice.
vii. If the action aligns with the preference, there is no discretion in the use of preference. As such, activities associated with the execution of preference are ministerial activities.
viii. Deviations from Options preference are discretionary activities and require the exercise of engineering judgment..
f. Background information (Support)
i. These represent statements that provide additional information about a traffic control device but which have no associated expectation of action.
ii. Support does not use any of the other operative words (shall, , should, or may).

Basis for recommendation: Keeping the current MUTCD structure will keep it simple and not confusing. The clarification of levels will provide greater flexibility to practitioners in those areas where flexibility is appropriate.

pg 43 Item 541.c. Change last bullet from “Sound” to “Acoustical”
pg 45 Item 542b. Change to read .
b. The content in this volume would be presented as standards, guidance, options, and support.

Pg 46 Item 546
a. Limit the size of a single rulemaking action to no more than 100 items identified in the Federal Register notice.
• i. Question: We are specifically asking for input on what is an appropriate value for the maximum number of significant items in a rulemaking.

I don’t think there should be a maximum value place on items in a rulemaking. If the responders to the docket feel that they need more time to respond they should request additional time from FHWA.

b. Extend the docket comment period for NPA rulemaking that has more than 100 items to encompass at least 2 NCUTCD meetings.
• i. Question: We are specifically looking for input on what is an appropriate value for the length of a docket period with a large number of Federal Register items.

The length of the docket period should be based upon the numbers of significant items in the docket.

pg 47 Add an item 549d. The US Access Board publishes a regulation (or regulatory notice) having implications and / or impacts on traffic control devices.

pg 47 item 552. Changes to MUTCD content should be proposed only if the changes are adequately justified by one or more of the following (see related item 519 for additional detail):
a. Insert ” international ” Widespread national or international experience.
b. Insert the phrase ” including safety and operational benefits to cyclist and pedestrians (including pedestrians with disabilities) ” Peer-reviewed and published research that indicate a safety, operational, or economic improvement including safety and operational benefits to cyclist and pedestrians (including pedestrians with disabilities)

CHAPTER 4: 1 RECOMMENDED STRATEGIC PLAN
No recommended changes
CHAPTER 5: 1 REFERENCES
pg 53 Add the website ARCHITECTURAL AND TRANSPORTATION BARRIERS COMPLIANCE BOARD (US ACCESS BOARD) http://www.access-board.gov
APPENDIX A: 1 CODE OF FEDERAL REGULATIONS 23 CFR 655 – No comment to Appendix A
Insert a new Appendix B ADA laws and regulations may affect the content of the MUTCD
Insert an Appendix B to add the ADA CFR 36 CFR Part 1190 or just add a summary (See information below) Then renumber the remaining appendixes
Title II of the Americans with Disabilities Act (ADA) requires that state and local governments ensure that persons with disabilities have access to the pedestrian routes in the public right of way.
The Department of Justice is the federal agency with responsibility for issuing regulations implementing the requirements of title II of the ADA and for coordinating federal agency compliance activities with respect to those requirements. Title II applies to the programs and activities of state and local governmental entities. The Department of Justice and the Department of Transportation share responsibility for enforcing the requirements of title II of the ADA with respect to the public right of way, including streets, roads, and highways.
The Americans with Disabilities Act (42 U.S.C. 12101 et seq.) is a federal civil rights law that prohibits discrimination against individuals with disabilities. Title II of the Americans with Disabilities Act covers state and local governments. The Department of Justice is responsible for issuing regulations to implement Title II of the Americans with Disabilities Act, except for the public transportation parts. The regulations issued by the Department of Justice include accessibility standards for the design, construction, and alteration of facilities (other than facilities used in the provision of public transportation covered by regulations issued by the Department of Transportation)..The Department of Justice’s accessibility standards adopt, with additions and modifications, the Access Board’s current guidelines, which are discussed below under the Need for Rulemaking.5 See 28 CFR 35.104 and 35.151.
The Department of Transportation is responsible for issuing regulations to implement the public transportation parts of Title II of the Americans with Disabilities Act.6 The regulations issued by the Department of Transportation include accessibility standards for the design, construction, and alteration of facilities used in the provision of public transportation covered by the public transportation parts of Title II of the Americans with Disabilities Act. The Department of Transportation’s accessibility standards adopt, with additions and modifications, the Access Board’s current guidelines, which are discussed below under the Need for Rulemaking. See 49 CFR 37.9 and Appendix A to 49 CFR part 37.
The Department of Justice is responsible for overall enforcement of Title II of the Americans with Disabilities Act. The Department of Justice has designated the Department of Transportation as the federal agency responsible for investigating complaints and conducting compliance reviews “relating to programs, services, and regulatory activities relating to transportation, including highways.” See 28 CFR 35.190 (b) (8).
APPENDIX B: HISTORY AND GROWTH OF THE MUTCD
pg 61 Add information to the table 4 about ADA information in parts 3,4,6 in the 2000,2003, 2009 editions
APPENDIX C: 1 REVISING THE MUTCD – No comment
APPENDIX D: 1 NATIONAL COMMITTEE ON UNIFORM TRAFFIC CONTROL DEVICES- No comment
APPENDIX E: 1 FUTURE OF TRAFFIC CONTROL DEVICES
No comment
APPENDIX F: 1 TARGET GROUP OF DRIVERS
pg 71- Change opening paragraph as noted in red :
The issue of which drivers traffic control devices are intended to serve is important as it 5 addresses the extent to which agencies should try to accommodate the needs of a wide variety of 6 drivers. It would be simple to say that traffic control devices should accommodate all drivers on 7 roadways. However, this is not a practical expectation. “The target road user includes pedestrians (including persons with disabilities) and bicycles. All public agencies and private entities responsible for TCDs need to accommodate the safety and mobility of these road users. There are some drivers that agencies 8 may not be able to accommodate. Examples include:.
October 16, 2013

1. Page 9, item 8.a., line 2. Based on my experiences in the vehicle emissions arena I submit that twenty years significantly understates the time it will take before current traffic controls are no longer needed. We will likely need to accomodate older vehicles, including antiques, for fifty plus years. To the extent that there may be socio-economic impacts associated with the incorporation of advanced technology on higher volume roads to the exclusion of current technology it could raise environmental justice issues.

2. Page 11, item 24: Compliance can take multiple forms. It could be the absence of an approved device where warranted, the presence of an unapproved or non-conforming device or the presence of a device that is not warranted. I concur with the opinion expressed and suggest that it also raises a question regarding whether state DOT’s should be charged with an oversight role vis-a-vis local and private roads.

3. As a general observation, a number of the statements characterized as “opinions” are facts. Item 29 on page 12 which lays out the shared responsibilities for implementation of the access requirements under the ADA is a good example. Consider differentiating between opinions and facts which may be best tendered as background considerations.

4. Page 11, item 22.a.i.: It is not the MUTCD’s definition as a national standard that gives it legal status. I suggest deleting current i and saying “Its incorporation into 23 C.F.R. 655.603 gives it the force and effect of a federal regulation.”

5. Page 11, item 25.e.: Strike “to tort liability lawsuits” and replace with “liability resulting from tort lawsuits.”

6. Page 13, item 32.a.i.: Not familiar with the concept of “long” versus “short” no passing zone definitions and suggest the incorporation of an explanatory parenthetical.

7. Page 13, item 32.b.iv.: Pennsylvania incorporates the MUTCD by reference into its regulations and provides supplemental material that includes, inter alia, traffic study elements, warrants, schematics and the implementation of certain responsibilities under the state’s veicle code. The state specific elements are primarily in addition to the MUTCD rather than in lieu of it.

8. Page 14, item 32.d.i.: Not significantly. Pennsylvania has sovereign immunity with a waiver for dangerous conditions of state highways but that liability is capped. Primary consideration is safety.

9. Pages 15-16, item 42.: Such a dialogue needs to take into consideration whether splitting the MUTCD as proposed would impact the ability of some states to incorporate by reference into their regulations those portions not subject to rulemaking.

10. Page 16, item 43, lines 4 and 5: Strike “tort liability laws” and replace with ” the law on tort liabilty.” This recognizes the fact that tort liability may be the product of the common law principles in some jurisdictions rather than statute.

11. Page 20, item 70: Respectfully disagree. Greater specificity plus reduced flexibility will likely translate into a greater exposure to liability because standards will be more rigidly applied, particularly by juries.

12. Page 22, item 76: Do not see the point or basis for including such an opinion. The individuals referenced in item 77 will use it because it is integral to their job just as they will utilize the AASHTO Green Book and other relevant publications.

13. Page 25, item 87.b.: Delete “is,” replace with “force and effect of” and delete parenthetical.

14. Page 32, item 507.a.i.: Suggest that consideration be given to development of review protocols to minimize conflicts between the ADA and its implementing regulations with the MUTCD.

15. Page 34, lines 30 and 32: They should be “guidelines” or “rules” but cannot be both. Rules provide direction, not guidance.

16. Page 34, item 516, line 39: Strike “irrelevant” and replace with “beyond its scope.”

17. Page 36, item 520: I have difficulty seeing how uniformity of expectations and consistency can be achieved if such procedures are not included.

18. Page 39, item 533.b.: I understand the rationale for the definitions but to the extent that the MUTCD has the force and effect of a regulation it is going to potentially be subject to the rules in each jurisdiction addressing the construction of regulations. In my experience the application of such rules to “shall” and “must” casts both as imperatives and they are considered as essentially synonomous. Even with the proposed definitions I therefore am concerned that in litigation a jury, and possibly even a judge, will afford “must” a higher level of mandate than it actually posesses. I would use “should” at the level set for “must” and something along the lines of “is advised to” in lieu of where “should” is currently used in subitem c.

19. Pages 45 — 48, MUTCD Revisions: The proposed protocol is intriguing. I cannot say that I have ever seen anything comparable, even for regulations of greater complexity and controversy than typically attends the MUTCD. My concern is that the consequence of the proposed limits could be a continual, unbroken stream of MUTCD related rulemakings.

20. Page 49, item 802: Not sure that the differences in exposure to tort liability from one state to another significantly impact the use of traffic control devices. Cases involving traffic control devices rarely arise primarily from circumstances where the MUTCD has been followed by a state. More common are cases where the MUTCD has not been followed or a deviation not adequately documented. In my experience most state actions are driven by safety considerations and sound engineering policy to the extent the state has the resources necessary for implementation. For states that do not have an economic defense to tort actions it would be far more beneficial to evaluate the effect of the phase-in periods/implementation obligations for new requirements to which a “shall” is attached.

October 15, 2013
Peter A. Speer
Vice President of Sales
Pexco LLC

Comments on the 20-Year Vision and Strategic Plan for the MUTCD

TRAFFIC CONTROL DEVICES AS INDEPENDENT ELEMENTS
Page 7, Line 16
Further to our comments of October 8th, the opinion stated on line 16 includes the word “curb” in addition to channelization. On line 10, you define “channelizing devices” as a traffic control device, and then 6 lines later state than an “infrastructure element” that channelizes traffic – such as lane separator curb systems and other channelizers – are not traffic control devices.

An initial section of the document defines traffic control devices as “all signs, signals, markings, channelizing devices or other devices that use colors, shapes, symbols, words, sounds and/or tactile information for the primary purpose of communicating a regulatory warning, or guidance message to road users on a highway, pedestrian facility, bikeway, pathway or private road open to public travel.” Under subpart “a.”, the section goes on to state the “Infrastructure elements that restrict the road users’ travel paths or vehicle speeds, such as curbs, speed humps, chicanes, channelization, and other raised roadway surfaces, are not traffic control devices.”

Pexco strongly objects to the inclusion of the words “curb” and “channelization” in the enumeration of devices that are “not traffic control devices.” The use of these terms both contradicts and may confuse the reader when “channelizing devices” is an enumerated term in the preceding paragraph.

A distinction should be made between curbs, an ambiguous term, and lane separators. Lane separators are commonly referred to as “curb systems” and are referenced in both 3H.01Channelizing Devices and 6F.72 Temporary Lane Separators the 2009 MUTCD.

Lane separators, as commonly used, are devices that utilize colors and channelizing upright elements complimentary to adjacent pavement markings safely guide motorists, and therefore meet the approved definition of traffic control devices as stated on page 7, line 10 – 14. They are in widespread use throughout the country and continue to be proven, low cost traffic safety solution.

Pexco recommends that the words “curb” and “channelization” be deleted from paragraph “1.a.”. Pexco further recommends that the sentence on page 7 line 10 be amended to read, “…signals, markings, lane separators and other channelizing devices…”.

Item 518, page 35, lines 9 to 12:.

“MUTCD content should be prepared so that it is precise, articulate, and easily understood by the intended users of the MUTCD.
a. Intended users of the MUTCD are the following user groups that represent practitioners responsible for conducting traffic control device activities.”

Reason for suggestion: The existing phrase – “and the level of mandate for the content” does not communicate well. Thus, it is recommended for deletion. “Useable” is vague in meaning. Thus, “usable” has been replaced by “precise, articulate, and easily understood”. The proposed wording explicitly states who are the intended users of the MUTCD the existing language does not do this.

Revise to read as follows: “the term engineer means an individual who”

Reason for suggestion: This wordsmithing provides for a simpler statement that is more direct and emphatic.

Item 518, page 35, lines 19 – 20:

Revise to read as follows: “the term engineer means an individual who”

Reason for suggestion: This wordsmithing provides for a simpler statement that is more direct and emphatic.

Item 531, Proposed MUTCD Section on MUTCD User:

Item 518 describes MUTCD users as Engineering, Technical, and Field. Why doesn’t Item 531 – proposed MUTCD language on MUTCD User also describe these three different classes of MUTCD users? I suggest that Item 531 should be expanded to identify these user groups.

COMMENTS WITH REGARD TO NCUTCD DRAFT VISION & STRATEGIC PLAN

Section provides a universal definition for Traffic Control Devices

“Traffic control devices are all signs, signals, markings, channelizing devices or other devices that use colors, shapes, symbols, words, sounds and/or tactile information for the primary purpose of communicating a regulatory, warning, or guidance message to road users on a highway, pedestrian facility, bikeway, pathway, or private road open to public travel.”

Further, Line #15, same opinion, states

“Infrastructure elements that restrict the road user’s travel paths or vehicle speeds, such as curbs, speed humps, chicanes, channelization, and other raised roadway surfaces, are not traffic control devices.”

Although these infrastructure elements identified herein may not meet the definition of a traffic control device, a distinction should be made between curbs, a nebulous term, and lane separators. Lane separators are commonly referred to as “curbing systems” and are referenced in both Chapters 3H (permanent applications) and 6F.72 (temporary applications) of the MUTCD.

Lane separators, as commonly used, are devices that utilize colors and channelizing uprights complimentary to adjacent pavement markings as well as tactile information to communicate messages to the road user, and therefore meet the approved definition of traffic control devices. They are in widespread use throughout the country and continue to be an effective strategy where other devices cannot be used.

In June of 2011, the Markings Technical Committee and the Edit Committee attempted to remove traffic lane separators from Part 3 of the Manual without industry’s input. (See below)

01 Channelizing devices, as described in Sections 6F.63 through 6F.73, and 6F.75, and as shown in Figure 6F-7, such as cones, tubular markers, vertical panels, and drums, lane separators, and raised islands, may be used for general traffic control purposes such as adding emphasis to reversible lane delineation, channelizing lines, or islands. Channelizing devices may also be used along a center line to preclude turns or along lane lines to preclude lane changing, as determined by engineering judgment.
Support:
01a Although not defined as traffic control devices, lane separators and raised islands can be used for channelizing purposes.

With that action in mind, if it is the intention of this document to further that effort and group lane separators with curbs, with the goal of having them eliminated from future editions of the MUTCD, then it will cause economic harm to companies who manufacture them as traffic control devices.

It would be our recommendation that traffic lane separators not be considered as an infrastructure element such as those listed on Lines 16, & 17, but rather included with the list of traffic control devices as listed with the definition for those devices.

Comments on Draft 20-Year VSP for MUTCD (version 7/18/2013)
Paul Carlson (Oct 9, 2013)

Congrats to Gene and others that assisted with the development of this document. There are many good thoughts and observations captured in the document. It can be overwhelming to think about the amount of work that is needed to pursue the ideas and concepts laid out. Personally, I am very much looking forward to participating in, and experiencing, the next 20 years of MUTCD evolution.

• One area that is not addressed adequately is the process currently used to draft new language and maintain the MUTCD. While the FHWA has some staff devoted to this job, the NCUTCD plays a key role as well. Page 1 briefly discusses the process in paragraph 2. What I was hoping to see in a subsequent part of the document was more thought and recommendations given to the process. My experience is that the NUCTD does as good of a job as is can given that it is nearly 100% volunteer effort and most work gets accomplished in the two 3-day meetings each year. If time is running short, or a topic is highly technical, the NCUTCD tends to move it along without proper consideration. Likewise, topics are dealt with individually which leads to unintended consequences regarding impacts on others areas in the MUTCD. Is the process the best that it can be? I would like to see how the process to develop and maintain the MUTCD compares to other significant documents such as the HSM or HCM. Those documents are developed and maintained through support by AAHSTO and TRB committee work. How can the Research Committee of the NUTCD work with other related committees such as the TRB TCD committee to develop NCHRP-like projects to provide resources for more thought and innovation regarding MUTCD formatting, language development, and other areas of improvement (see Item 65 on Page 20). I would like to see some additional language added regarding the need to reassess how MUTCD material is developed and how the MUTCD is maintained. I’m not talking about taking it out of the FHWA jurisdiction, I’m talking about how to improve the near-100% volunteer effort that FHWA relies on now.

• One of the items that makes it difficult to provide national uniformity in all areas is the winter maintenance activities of northern tier states. I didn’t see this item mentioned. Specific examples of applications that it can impact are:
o Use of RRPMs for nighttime delineation (versus delineators or other roadside devices)
o Non-uniformity of marking condition throughout a calendar year, which limits the functionality of V2I potential such LDW systems
o Justification of overhead sign lights in areas of snow

• Another item I didn’t see included but I’ve heard discussion about is the need to start documenting the justification for specific decisions regarding changes or additions to the MUTCD. Some of that is captured in the rule-making process. It seems like a reference document could be developed to catalog decision thinking, reports, data, etc. that were used to make specific changes or additions. Each section of the MUTCD could have a reference number that would refer to a specific item in the reference document.

• Section 530
o Where does driver understand fall within the definitions listed?
o Within appearance, should brightness, intensity, flash pattern/rate, etc be included?
o Under installation, what about reaction time?
o Where does the discussion come into play about upgrading to meet new regulations such as moving from 8 to 12 inch signal lens, all cap SNSs to initial cap SNSs, etc. To me, this would be a new subitem in 530.

• Section 533
o I think these added terms go against the effort to simplify the MUTCD
o Can the author provide multiple specific examples for each term (to help with understanding)?
o Consistent Standard and Guidance seem way too similar without some examples.
o I specifically disagree with use of the “ought” term. It’s not even in Microsoft Word’s dictionary and in my mind has the same meaning as “should.” But probably more importantly, if you Google “ought vs should” you will see that those who love the English language like we love TCDs think that ought is more explicit than should. If these terms are eventually used in the Manual, they need to be fully vetted.
o Let’s consider an example. The most commonly recognized TCD in the world…the Stop sign. I assume that the red background with white letters would be a “Uniform Standard.” However, both color red and white are not exact. There are different criteria for their daytime and nighttime performance…and that criteria include a range of performance levels. Based on the way the terms are explained, color of a Stop sign would then be a “Consistent Standard.” And if so, deviations could be justified. I don’t think that is the intent here. This is one of probably many loop holes in the way these terms have been proposed.

• I’m wondering if we could develop a protocol/process of new material. Most new items are considered piecemeal and sometimes in a hurried fashion without understanding how other Parts of the Manual might be impacted.

• In Chapter 4, I would like to see specifics on how the Research Committee of the NCUTCD can help drive new processes for the NCUTCD or FHWA. I’m currently thinking that they can develop problem statements for NCHRP or FHWA funding that allow time and energy (beyond volunteer work) to be spent working on various high level items such as developing ideas and examples of streamlined MUTCD Parts, developing a pilot reference document for a specific Part of the Manual, developing PSs aimed at strategic growth areas such as full-matrix signing, LED signing, V2I items, adaptive signing, etc. There should be an outline of how the Research Committee can coordinate and partner with other organizations to facilitate long-term funding to support the MUTCD.

• The CFR language in Appendix A is interesting. I have not read it in a long time. It does remind me of an issue that I have always had with 1A.09 which reads, “This Manual describes the applications of TCDs, but shall not be a legal requirement for their installation.” To me, this statement is meant to say that the MUTCD was not written to say when you shall install a device. Only that devices shall be uniform…such as a Stop sign being 8-sided with red background and white STOP and white border. However, the Manual has many places with requirements of application, such as 2C.06.

• In the Growth Appendix B, I would like to see comparisons to other documents to put the growth of the MUTCD into perspective. Showing its growth in isolation is a little misleading. See Scott Wainwright’s comment of Aug 2 concerning growth of shall statements being misleading with respect to perception of ‘09 Manual being more prescriptive.

• I can’t remember where, but somewhere in the VSP there is a discussion about assessing the economic impact of MUTCD changes/additions. I would like to see more discussion on that topic.

• Since the 2009 Manual was issued, the FHWA has seemed to back off of compliance dates for new regulations. I think a lot of agencies saw that as a good thing but I’m not so sure it is. If there is no compliance date, then agencies are supposed to address non-compliant devices via “systematic-upgrades.” See MUTCD Intro, I-3. There is no timeline set for systematic replacement and agencies are then left to decide when to upgrade. They might wait for the device to become worn out, knocked down, vandalized, etc. The longer agencies wait to upgrade, the more liability risk they incur. Without specific compliance dates, many agencies loose the justification needed to allocate funds to upgrade specific devices. As a result, the upgrades are slow to be implemented, and are implemented at various times throughout the country, leading to non-uniformity and more exposure to tort claims. I would like to see some discussion in the VSP on this topic. Maybe I’m off base here.

• Probably the most significant issue in 2013 regarding the Manual is the FHWA effort to “streamline” the document. There is very little information in the VSP concerning this on-going effort. Maybe by design. If so, can there be a note added to explain?

The following comments represents and overview of the thoughts of members of the Traffic Engineering staff at the Massachusetts Department of Transportation and summarized by State Traffic Engineer, Neil Boudreau.

Item 505 – This statement is the key to defining what is considered a uniform standard versus a consistent standard (Item 533). Some TCD’s exhibit principles that make them firm or uniform standards, i.e. a stop sign has an octagonal shape and is always white legend on red background, or that a green colored light has a defined meaning, regardless of application type. However, unique geometric and/or environmental conditions specific to a part of the country provides justification to allow for deviation from the intended “standard” use of the TCD.

Item 512 – Concern as to how “weak” the legal requirement to follow standards would be, if practitioners had broad leeway to develop context-sensitive solutions. We find very different issues in following the Green Book to the letter versus following the MUTCD to the letter. I find that the concept of allowing flexibility in the type of standard (Item 533) provides transportation agencies with a means to employ engineering judgment, but use of CSS will take this too far and weaken the governance of the MUTCD.

Item 520 – Discussion mentions excessive use of traffic control devices. It would be good to have some stronger language cautioning against unnecessary signage that are used in blanket installations (I’m thinking of R10-12 and W13-1P, in particular). The tendency right now is to ignore the language that’s already in the MUTCD requiring engineering study before use of certain signs, e.g. W13-1P.

Item 533 – Splitting verbs into shall, must, should, may, and ought seems to be unnecessarily complicated. The current system (shall, should, may) works fairly well and can only be enhanced by the clarification on the type of a standard that would offer the use of “Uniform” and “Consistent” sub-categories. Use of terms like preference or support should be reserved for use in an updated practitioner guide.

Item 536 – If implemented, MUTCD should include a summary table listing the Uniform requirements (verb “shall”) contained within.

Item 538 – I am in agreement with keeping the MUTCD as a single document. Expanded use of hotlinks/smart tags would be very welcome. Combining or linking content from the SHSM, which is now a separate document from the MUTCD, would make designing traffic plans easier.

Item 540 – If the MUTCD is to be split into separate volumes it would make practitioner use of the MUTCD much more difficult because related information that is now in a single section (or a handful of adjacent sections) would potentially be split into three different areas, 1 in each volume. This is similar to the situation we experience now in having the MUTCD and SHSM being contained in separate but seemingly related documents.

NOTE: I am in agreement with the premise of the suggestion presented by Jonathan Upchurch on July 29, 2013 at 5:35 pm that would keep the ultimate updated MUTCD into 3 Divisions within one main document. “Item 540 – The MUTCD for the mid-2030s should be structured as a single document with three major divisions, as listed below and as described in Items 541 through 543.
a. Division 1: Definitions, Meaning, and Appearance
b. Division 2: Use, Operation, and Removal
c. Division 3: Installation and Maintenance (Typical Applications)”
Reason for Suggestion: To most people the word “Volume” means a separately bound book. Thus, when readers read Items 540 to 543 [in the July 18 version] they will think that the MUTCD would be divided into three separate documents. My understanding of the intent of Item 540 is to have a single document, but the July 18 version wording is confusing.
Item 545 – Revisions, particularly to correct simple errors, but also to incorporate interim approvals, should be published on a somewhat regular schedule of every 2-3 years.

Item 546 – The proposed answers to Questions 546 a. and 546 b. provide a reasonable number of items to be considered for rulemaking.

Item 548 – Full agreement on the justification for gaining the insight, knowledge and support of the membership of the NCUTCD as a defined component of the Federal Rule Making Process.

Item 552 – Full agreement on the need to obtain proper justification for introducing proposed changes to the MUTCD via the rulemaking process.

Items 801, 802 and 803 – While the intention of the MUTCD is to provide uniformity to the practice and implementation of Traffic Engineering, the notion that we will ever get to a point where a “one size fits all” document is impractical. By the pure basis that this country was founded and affords the states the ability to set general laws to govern their territory, we may never find a means to achieve full compliance with the “national” MUTCD.

Item 809 (b) – Next MUTCD should incorporate some larger changes, particularly regarding ADA compliance, bicycle treatments (bike signals, treatments for roundabouts), and RR crossings (incl. LRT/BRT in exclusive or shared ROW crossing or sharing space on urban streets).

Chapter 2, Item 5 (page 8, line 16) – Consider changing “public roadways” to “within the public right-of-way”

Chapter 2, Item 8.a (page 9, line 2) – The duration statement of “for at least twenty years” may not be appropriate for all users and agencies. Consider changing or deleting the specific numerical reference, perhaps with “for the foreseeable future”

Chapter 2, Item 48.c (page 16, line 45) – Regarding the question put forth, the statement “a manual with requirements, recommendations, and options” would be my preference

Chapter 2, Item 50 (page 17, line 6) – Regarding the question of the intended meaning of the word “uniformity,” I would offer that uniformity is defined as having consistent meaning and clear expectations of adherence behavior for the intended audience.

Chapter 2, Item 58.a.i (page 18, lines 28-30) – Given the diversity of intersection configurations across the nation, it may be too difficult to create a “typical” application for intersection control to illustrate “all signing to be used on the approaches and departures to the intersection…”

Chapter 2, Item 85 (page 25, line 16) – Regarding the question of should the MUTCD content be written with a traffic engineer as the intended audience, my response is “yes!” By all means, the MUTCD should be written for an audience that is professionally licensed to practice engineering, with specific expertise in the field of transportation.

Chapter 2, Item 86 (page 25, lines 21-23) – Regarding the question of writing the MUTCD so non-engineers can make decisions regarding specific traffic control device activities, my response is “no!” The MUTCD should be written so that reasonable people with similar training and experience would make the same decisions regarding the placement and operation of traffic control devices.

Chapter 2, Item 111 (page 29, lines 16-17) – Regarding the question of the degree of review on studies to support changes to the MUTCD, I suggest that all studies should be reviewed and approved by the FHWA.

Chapter 2, Item 121 (page 30, lines 37-38) – Regarding the question of the best way to deal with the development of innovative traffic control devices, I would respond that it is through the existing experimentation process.

Chapter 3, Item 528.b (page 37, line 29) – I suggest changing “pedestrians” to “other users not operating a vehicle,” since target road users include people on segways, roller skates, skateboards, as well as passengers in vehicles (who sometimes assist in interpreting traffic control device meanings and communicating that to the driver of a vehicle).

October 08, 2013
Peter A. Speer
Vice President of Sales
Pexco LLC

Comments on the 20-Year Vision and Strategic Plan for the MUTCD

TRAFFIC CONTROL DEVICES AS INDEPENDENT ELEMENTS
Page 7, Line 16
The statement on channelization is confusing and contradictory. On line 10, you define “channelizing devices” as a traffic control device, and then 6 lines later state than an “infrastructure element” that channelizes traffic is not a traffic control device.

An initial section of the document defines traffic control devices as “all signs, signals, markings, channelizing devices or other devices that use colors, shapes, symbols, words, sounds and/or tactile information for the primary purpose of communicating a regulatory warning, or guidance message to road users on a highway, pedestrian facility, bikeway, pathway or private road open to public travel.” Under subpart “a.”, the section goes on to state the “Infrastructure elements that restrict the road users’ travel paths or vehicle speeds, such as curbs, speed humps, chicanes, channelization, and other raised roadway surfaces, are not traffic control devices.”

Pexco strongly objects to the inclusion of “channelization” in the enumeration of devices that are “not traffic control devices.” The use of this term both contradicts and may confuse the reader when “channelizing devices” is an enumerated term in the preceding paragraph.

Pexco recommends that the word “channelization” be deleted from paragraph “1.a.”

MUTCD AS AN AUTHORITATIVE REFERENCE DOCUMENT
Page 12, line 36
Pexco agrees with John Fisher’s comments of January 20, 2013: “I strongly believe that the application, location/placement, operation, maintenance and removal of TCDs are valid purposes of the MUTCD. These aspects of TCDs are vital for promoting uniformity and improving traffic safety and therefore should be part of the “national standard”.”

Page 15, line 33
Pexco strongly disagrees with the stated “need to limit the amount of material that can be included in the document”. Pexco agrees with John Fisher’s comments of January 20, 2013: “The MUTCD has not experienced a notable surge in the level of detail associated with traditional TCDs. Rather, the MUTCD has embraced many new TCDs and has addressed multi-modal needs for which new MUTCD provisions have been developed. Consider how technology has led to an increase in the types of TCDs, such as in-pavement warning lights, embedded lights on warning signs, blank-out symbol signs, etc. Also, consider how the need to address other road users, such as older and handicapped pedestrians, bicyclists, light rail transit, toll and managed lanes, etc., has led to new provisions on how best to serve them. Naturally, the more technology and modes that are addressed the larger the MUTCD becomes. It would not be an option to avoid expansion of the MUTCD by ignoring advances in technology and enlightened thinking regarding multi-modal needs. Besides, the size of the MUTCD should not be a concern, since it is available in electronic format.”

Pexco further agrees with the comments made by Scott Wainwright August 08, 2012: “I don’t believe that other important standards, such as building codes, electrical codes, zoning ordinances, etc. artificially limit the size of their documents if the material is deemed important, as TCD uniformity certainly is. Size of document is immaterial when smart search engines, cross-indexing, hot links, pop-ups, etc. are available and used to make it easy for a user to find what he or she needs.”

MUTCD USE AND USERS
Page 25, line 3
Pexco agrees with John Fisher’s comments of January 20, 2013: “I believe that the proposed target audience is too narrow. If the target audience is limited to only professional traffic engineers with extensive experience, then the MUTCD would not be accessible to nor comprehended by those with less experience who aspire to master knowledge of the “national standard”…. The reality is that there is no single audience for the MUTCD. While the core audience may be those who have responsibility for TCDs, the term, “target audience” tends to be exclusive. The MUTCD needs to be written for an inclusive audience since a variety of users depends on it to one degree or another. In summary, the audience should be “all those who play a role in planning, designing, operating and maintaining TCDs.”

FUNDAMENTAL ASSUMPTIONS
Page 32, line 5
Pexco strongly disagrees with 503.c.i. stating that “size is not an appearance characteristic”. This is completely nonsensical and this item should be deleted. All you have to do is take a look at Figure 6F-7 Channelizing Devices to see that size matters! From minimum heights on drums to minimum widths on Type 2 barricades, size clearly establishes uniform characteristics across the nation. If you are creating a “national standard” for uniform traffic control devices, the size of the device MUST be included.

Pexco also strongly disagrees with the inclusion of the word “size” in the second sentence of 503.f and recommends that word be deleted from that sentence.

FUNDAMENTAL RECOMMENDATIONS
Page 35, line 9
Pexco strongly disagrees with Guiding Rule #519. Guiding Rule # 519 is overly prescriptive regarding peer review of research. As a private sector company we invest considerable resources of time, personnel and money in the development of new devices or the improvement of existing devices. In return, we expect a reasonable “Return on Investment”. Delays in bringing these devices to market adversely affect our return. We frequently submit research regarding the effectiveness of our products directly submitted to the FHWA which as the owner of the MUTCD should be able to make a decision as to whether that research is sufficient to include the device in the Manual. “Peer review” is an overly academic process that would cause an inordinate and unjustifiable delay in the introduction of the device, thus adversely affecting ROI and possibly delaying the deployment of life saving devices.

MUTCD CONTENT
Page 42, line 11
Pexco strongly disagrees with #537 which proposes that “When new traffic control device principles are added to the MUTCD, they should typically be introduced as non-mandatory practices and maintained as such for at least one edition of the MUTCD.” As stated above, research is conducted before the introduction of new devices into the Manual. That research should serve as the basis for a decision as to whether a practice is mandatory or not. It seems counterintuitive to wait for an entire MUTCD cycle, recommended to be 8 or 10 years, to institute a practice that may support our national goal of moving Toward Zero Deaths.

MUTCD REVISIONS
Page 45, line 43
Pexco believes that a schedule to revise the Manual every 8 – 10 years is far too infrequent given the pace of change of technology today. As previously discussed, as a private entity we often make considerable financial investment in the development of new products, especially those that advance safety. We believe that principles and practices to implement proven new technologies should be introduced to the Manual as quickly as those technologies are available. This objective would lead one to conclude that the time between revisions should be shorter, rather than longer.

Page 47, line 37
Pexco disagrees with recommendation #552.b. which suggests that changes to the MUTCD should require research that is published and “peer reviewed.” As stated earlier, as a private market company we look to gain a return on investment (ROI) on new products. There is a direct element of that ROI which is linked to the amount of time it takes from product research and development to product deployment. Peer reviews equate to longer times which equate to a reduced ROI. Pexco believes that FHWA is perfectly capable of reviewing research and making a decision as to whether a new or updated device(s) should be included in a NPA for the Manual.

Pexco also believes that in the near future the primary venue for the MUTCD will be e-technology based. Given that assumption, we have very little concern about the size of the document in terms of page count and more concern about the organization and ease of “search functions” especially on smaller (i.e. hand-held) devices.

APPENDIX B:
Page 59, line 20
Pexco disagrees the conclusion that simply because there are more shall’s and should’s in the 2009 MUTCD, it is therefore more prescriptive. Pexco agrees with Scott Wainwright’s comments of August 2, 2013: “The last 2 sentences (lines 18-22) of the 2nd paragraph on page 59 in Appendix B should be re-written to say: “The number of shall and should statements in the 2009 MUTCD has grown significantly from the 2003 MUTCD, as shown in Table 3. This increase is due predominantly to the addition of new devices and new topics that were not in the 2003 edition, such as flashing yellow and flashing red arrow turn signal displays, automated flagger assistance devices (AFADs), toll road/toll plaza signing, signing for managed lanes, community wayfinding signs, and more than 50 other unique new devices or revisions in devices that were deemed by NCUTCD and/or FHWA as being needed to address new technology, emerging new applications such as electronic toll collection, and device improvements as found effective by research (see Table 4.)”

Section 514: It is not clear whether this section applies only to public agencies or whether is applies also to private contractors. I recommend revising (a) to include private contractors. Same comment for Section 518
Section 522: Do not agree. Change wording perhaps, “The MUTCD should serve all intended users and provide an appropriate level of educational portions.”
Sectrion 523: Agree fear of tort liability should not dictate language or decision to include/not include subjects. Add, “Language, phrases, should not be compiled to attempt dictation of liablity issues.”
Section 540-543: “The 2030s MUTCD should be structured in manner of technical devices and programming available at that time and not dictated by this 2014 document.”
Section 533: See difficulty in presenting six new levels of definition types, leave with current four.
Section 531: “Those individuals trained and certified as work zone traffic control supervisors shall not excercise discretionary activities.”
Section 546: “Single comment to NPA are welcome but should not dictate a change to MUTCD based on one comment from Water Valley, Texas.”
Section 808: Suggests no changes in MUTCD for next two editions. That seems to say we will meet for many meetings beginning now but not make significant changes until the 2025 edition. If true, why would state and local governments approve travel to our meetings.

The statutes and regulations regarding traffic control devices and their application are for the purpose of developing and implementing a uniform system of traffic control devices, and the purpose of the MUTCD is to serve as a complete and authoritative reference for the the application, design, use and operation of this system.

We should consider a lesson learned many years ago by the railroads. The railroads have uniformity issues equivalent, at least, to those which we face in the highway mode. Their issues involve many aspects of their business including track, tunnel and bridge engineering criteria for car clearances interoperability of signals and communications and handling cars at interchange, to name a few.

The word “standard” is not used in that industry. Although every aspect of railroad engineering and operation is addressed through the American Railway Engineering and Maintenance of Way Association (AREMA) and published in a voluminous Manual, the various aspects of their efforts are published as “Recommended Practices”. The AREMA Recommended Practices are applied to railroads in Canada, the US and Mexico.

AREMA defines Recommended Practics as:

“. . . a material, device, design, plan, specification, principle or practice recommended to the railways for use as required, either exactly as presented or with such modifications as may be necessary or desirable to meet the needs of individual railways, but in either event, with a view to promoting efficiency and economy in the location, construction, operation or maintenance of railways. It is not intended to imply that other practices may not be equally acceptable.”

If we are able to develop some similar terms or definitions for the MUTCD, it would go a long way toward resolving the current issues surrounding the current levels of mandate.

And, we need to continually keep the most basicquestion in Traffic Engineering in mind. It is, “What does the driver see?”.

Item 68a and Appendix B. I concur with Scott Wainwright’s comments dated August 2nd and his proposed changes to the draft Vision and Strategic Plan. Scott’s proposals are to delete Item 68a and to make changes to Appendix B.
The perception that the 2009 MUTCD is much more prescriptive has taken on a life of its own – without underlying evidence to support the contention that the 2009 edition is more prescriptive. Scott presents objective data to show that the perception is untrue.
Scott Wainwright’s analysis shows that the increase in “shalls” is mostly the result of new material added to the Manual, rather than a large “swing” in the use of “shalls” that reduces the ability to use engineering judgment.

I have attempted to dig a little deeper into “the weeds”. The number of “shalls” in the 2009 edition is 914 more than in 2003. Scott reports that 762 of 914 new “shalls” were the result of the addition of new topics and new devices that were not in the 2003 MUTCD. I asked Scott if it would be correct to conclude that the balance of 152 “shalls” reflected instances in which the MUTCD became more prescriptive (such as changing from “should” to “shalls”). Here is Scott’s reply.
“There was a lot of re-writing, reorganization, repetition, etc. of 2003 text that took place in producing the 2009 editions. I feel certain that there weren’t 152 “should” or “mays” that got strengthened to “shalls”. I believe most of the 152 resulted from consciously deciding to repeat certain sentences in a given section into a different section and/or different part – for emphasis, for clarity, to make it easier on users by eliminating the need to follow a cross-reference back to a different place in the Manual. I think some others resulted from re-writing sentences for clarity and in doing so it resulted in some additional “shalls” — not more actual requirements, but more occurrences of the word.”

Scott concluded by stating that he felt that instances in which “should” were upgraded to “shalls” probably constituted only about a one percent increase in the number of “shalls”.

The above information further emphasizes that the 2009 edition did not “tighten the screws” and impose more requirements to the extent that many believe.

General: Dwight Kingsbury makes many good points in his comments submitted on August 20th. My following comments complement Dwight’s comments and emphasize the need for the Vision and Strategic Plan to say more about streamlining.
As of late June, 2013 the focus of the Federal Highway Administration is on “streamlining” the MUTCD. “Streamlining” undoubtedly means different things to different people. To some, the concept of “streamlining” may simply equate to creating an MUTCD that is smaller in size. A better description of “streamlining” – in my view – would be: “improving the ease of use of the MUTCD”. There are a variety of ways in which ease of use could be improved. The following is a partial list of ways included in Chung Eng’s June 27 presentation to the National Committee.
• Develop smart search apps
• Improve organization of content reorganize content where opportunities for improving flow are identified
• Eliminate redundancy and unnecessary language
• Provide cross-indexing
• Provide info in modular or tabular format
• Provide more hotlinks and pop-ups
• Better position figures with associated text
• Use more summary tables and figures to reduce text
• Reorganize / reconfigure existing figures to better manage space

The 20-Year Vision and Strategic Plan is almost completely silent on streamlining. Item 61 points out that “The MUTCD is a large and complex document.” Item 67 notes that “The size of the MUTCD can make it challenging to use….”. Item 69 states that “There is a need to reduce complexity of the MUTCD….” and offers some ways to do so. However, the Vision and the Strategic Plan make no recommendations for streamlining the MUTCD. The Strategic Plan description makes no recommendations on streamlining for any of the proposed editions of the MUTCD – 2018, 2025, or 2033 – other than smart tags for the 2033 edition. This is a major shortcoming.

I suggest that an additional Item be added under Fundamental Recommendations in the Recommended Vision.

Item 5XX. The MUTCD should be produced in the form, format, and content that provides the best possible ease of use by the user.

I suggest that Item 808 be revised as follows.

Item 808. The emphasis areas for developing the 2018 MUTCD should be:
a. restructuring of the levels of mandate within the 2009 MUTCD
b. streamlining the MUTCD to improve ease of use.

I also suggest that a new item be added, as follows.

Item 8XX. Streamlining can include, but not be limited to, the following approaches to improve ease of use of the MUTCD.
a. Develop smart search apps
b. Improve organization of content reorganize content where opportunities for improving flow are identified
c. Eliminate redundancy and unnecessary language
d. Provide cross-indexing
e. Provide info in modular or tabular format
f. Provide more hotlinks and pop-ups
g. Better position figures with associated text
h. Use more summary tables and figures to reduce text
i. Reorganize / reconfigure existing figures to better manage space
j. Improve consistency on what information about devices is presented
k. Provide subheadings to help a user find information on a particular subtopic

No. 537, I would like to see all new devices added to the MUTCD as optional and kept there for a least one full cycle before becoming recommended and at least two full cycles before becoming mandatory. This way, the agencies who are having the problems that the devices are designed to address can use them while the agencies not having the problems can schedule upgrades more systematically, assuming that they ever do become universal. This also would help to avoid some of the issues mentioned by various of the State DOT’s whereby FHWA made them prioritize their safety priorities (through the Strategic Highway Safety Plans), which having approved, FHWA then preempted by forcing resources to spent making devices uniform despite demonstrated safety needs elsewhere.

No. 551, the cost of updating infrastructure should look not only at items mandated by the MUTCD but also at costs due to industry trends and other government agencies. A perfect example of this is the changes pedestrian heads. The mandated change from Walk/Don’t Walk to Man/Hand generally coincided with the industry wide shift to LED, resulting in a smooth upgrade at fairly minimal additional cost (it helped that Man/Hand had been an option since at least the 1989 MUTCD). The change to countdown is being a lot more painful as all of the new LED pedestrian signals are being forced out long before the end of their useful service life.

I did not see it covered in any of the bullets, however I think that the practice of providing compliance dates for MUTCD changes should be resurrected. If the costs of implementing a specific change within a reasonable time are astronomical, perhaps FHWA should reconsider whether the change being discussed is really all that important.

In terms of restructuring the MUTCD so that portions are not adopted by a formal rule-making, I fear that within a few short years the non-mandatory portions of the MUTCD will have not of been updated in a timely fashion, resulting in ever-growing inconsistencies between the mandatory portion and the other portion. This worry is based in part on FHWA’s seeming inability to publish the Standard Highway Signs and Marking book in time to support a new MUTCD edition and in part from seeing what has happened to documents like the Traffic Control Devices Handbook.

General Note: The MUTCD authors need to be aware that automated (autonomous, self-driving, driverless) vehicle technology is advancing at such a rapid rate that Google have indicated that they aspire to have vehicle technology capable of unmanned operation in public hands by 2017. Having researched this subject in depth and breadth for the last two years, and attended the TRB Workshop on Road Vehicle Automation on both years that it has been held I am satisfied that this Google aspiration is both credible and highly probable. This therefore potentially impacts on the MUTCD in a number of interesting ways – not least of which we would have a completely new type of road user that was never envisaged in the previous incarnations of this document. Following I will refer to vehicles capable of NHTSA Level 4 automation as Automated Vehicles (AVs):

Page 33, Chpt 3, 528. Section 1A.XX Target Road Users:
Suggest a new sub-section ‘c.’ that encompasses this completely new type of road user – it would be best to refer to the laws in Nevada, Florida, California and District of Columbia for the appropriate definitions.

Page 45, Chpt 3, 544
Given the transformative nature of AVs, and their potential to dominate road transportation in possibly as few as 15 years, then it may be appropriate to consider a major revision of the MUTCD well in advance of 8-10 years.
This could be seen as an outworking of 545, d.

Page 69, line 6
Change: “Fully automated vehicles on selected major facilities” to simply “Fully automated vehicles capable of unmanned travel” or, “Fully automated vehicles capable of NHTSA Level 4 automation.”
Google have categorically stated that they are developing their technology to operate on the existing road network, and to not require any specific infrastructure changes. To suggest that their use be limited to ‘major facilities’ therefore seems to be seeking to lead the technology development, and inappropriate.

When both the Automated and Connected Vehicle Technologies are considered, as well as the potential for the implementation of Automated Vehicle Zones where manually driven vehicles will only be permitted in certain circumstances, then a whole new area of the MUTCD could be developed where the primary aim is to communicate the road scenario to a ‘robot’, rather than to humans.

This is to propose inclusion of an item in the section on “MUTCD Structure” to recommend reorganization of some MUTCD sections for purposes of enhancing consistency of presentation of device information.

After the summer 2013 NCUTCD meeting, Jonathan Upchurch called my attention to the fact that, although FHWA’s presentation at the meeting expressed interest in pursuing their initiative to “streamline” and simplify use of the MUTCD (without splitting the Manual, as they had initially proposed) and suggested various reorganizational measures that might be undertaken to accomplish this, the current draft VSP says almost nothing about streamlining.

The draft acknowledges the difficulty of using the current Manual in a number of items. Item 56 describes a few of the Manual’s organizational characteristics that challenge users. Item 59 asserts a need “to improve the structure and organization” of the MUTCD. Item 69 observes that the MUTCD is “complex, cumbersome, and challenging to use”.

In the section on “MUTCD Structure”, item 538 discusses use of smart tags (as an internal cross-referencing tool) to simplify use of the MUTCD, but no other measure for simplifying use is mentioned. Even with smart tags, lack of consistency in the presentation of information about different devices and applications, and the sheer piling on of quantities of text in some sections, without content-related subheadings or other navigational aids, would still challenge users.

In their NCUTCD presentation, FHWA included a list of ideas for “streamlining” the Manual that included

-Improve organization of content reorganize content where opportunities for improving flow are identified
-Provide info in modular or tabular format

Presumably modular or tabular formatting might minimally involve identifying the topics of portions of existing text within a section (e.g., “Device purpose” or “Intended meaning”, “Device design”, “Criteria for use”, “Placement”, “Combination with related devices”, “Co-installation with other device(s)”, “Alternate device/treatment for same purpose”, etc.) by means of subheadings, or labels in a parallel table column or in the margins, or organization of topics within labeled text boxes and sidebars.

While such a modular or tabular reformatting should be helpful, it would allow (in a minimal implementation, with no changes in existing text of a section) existing inconsistencies in the types of information presented in different sections and chapters to remain, with resulting potential for confusion. By making such inconsistencies more apparent, it might conceivably even increase potential for confusion, by allowing unintended inferences (i.e., by suggesting that if a given section has nothing to say about some aspect of usage of a discussed device, even though the same aspect of usage is clearly addressed in a nearby section that describes other devices, then the Manual has nothing to say about that aspect for the given device).

In some sections, for example, the Manual explicitly discusses placement of a device, whereas other sections that describe devices are silent about placement, because placement guidelines are provided in a separate section the Manual user is expected to be familiar with or, at least, to find and consult. Similarly, many sections present specific criteria for use of a device, whereas the criterion in 1A.08 P03 is mentioned only in that section any user contemplating use of a regulatory device is presumed to be familiar with that section.

Other inconsistencies involve the way in which an optional use is allowed or implied. In many sections, an Option statement explicitly allows some application of a device. In 2C.50, though, a Standard statement (P04) describes a condition on the use of certain non-vehicular warning signs at (pedestrian, snowmobile, and equestrian) crossing locations, even though no preceding Option statement in the section mentions permission of such use the Standard statement implicitly indicates that some otherwise undescribed applications are permitted, functioning as a de facto combination Standard-Option statement. Such inconsistencies blur the function of Standard statements and lend support to the “permissive” interpretation of device usage (i.e., that plausible but unmentioned uses of an optional device are permissible unless explicitly prohibited).

Therefore, beyond simply reorganizing content for better “flow” within sections, and reformatting content within sections, it may be helpful to make sections more self-contained by incorporating, where this is not already done, a brief (hotlinked) reference to content relevant to a device that is presented in another section. Also, where permission to use an (otherwise unmentioned) application of a device is presently implied by a Standard or Guidance statement, it may be helpful to introduce a preceding Option statement that explicitly allows the application.

Such additions to sections might superficially seem inconsistent with FHWA’s suggestion (for streamlining) to “Eliminate redundancy and unnecessary language”. However, “redundant” text included in some sections may well have been motivated by a recognition of the confusion and oversights that can arise when aspects of usage of a device are addressed in other sections not referenced in the section that most specifically introduces and describes use of the device. If “device-introducing” sections were reformatted in a more self-contained modular or tabular fashion, the presentation would not necessarily increase the length of the Manual, because such formatting can eliminate the need for complete sentences. Instead of using a complete sentence to refer the user to section NL.NN for some aspect of device usage, for example, a simple link to “NL.NN” could be inserted in an appropriately labeled table cell (e.g., “Placement”).

Such reorganization and formatting could make the MUTCD a more “transparent” document.

I therefore suggest that a new item be inserted in the section on “MUTCD Structure”, following item 538, to address streamlining measures. The new item could quote or paraphrase the bullet points quoted above (as Jonathan discussed with me–I think he intends to post another comment here), but should additionally clarify that reorganization could be undertaken not merely for purposes of “improving flow”, as FHWA seems to anticipate, but for purposes of increasing the consistency of presentation in sections primarily concerned with introducing and describing specific devices, as discussed above. This could be done by including, in the new item’s list of streamlining measures, some wording like:

“Improve the consistency of presentation in sections that introduce use of specific devices, by exploiting modular or tabular reformatting to include internal links to make such sections more consistently self-contained and transparent, and to present all optional applications as explicit Options”.

540 “should be structured as a multi-volume single document” Keep the MUTCD as a single document single volume.

This library is an ongoing project designed to facilitate access to financial and economic data. It tries to cover potentially useful or interesting data points but unfortunately some functions will only return single point data which however could be aggregated over time to construct a limited time series. On the other hand, some functions that retrieve large amounts of data or depending on the data source will take some time to run. See the function index for more information on issues of data availability and relative run time.

The company fundamentals module includes functions to retrive data from Yahoo Finance , MarketWatch , The Motley Fool , Finviz and Macrotrends . The price data module retrieves data from Yahoo Finance and CBOE . The news module enables historical news headline collection from the FT , NYT , WSJ , Barrons and Seeking Alpha based on keyword searches. The library also provides a function to get all Nasdaq-listed stock tickers as well as worldwide stock symbols (these need some cleaning still once retrieved).

If there are any issues, ideas or recommendations please feel free to reach out.

• Refactor the news scrape..
• Rework economic data module

Python3 is required. Google Chrome version 89.*.****.*** or higher is required for some functions involving Selenium (can be found here).

Note that Selenium may not be able to use Chrome in combination with Firewalls and the functions may fail to execute..

### Requirements

The functions below enable you to download financial statements, valuation ratios and key financial statistics as well as analyst ratings, insider transactions, ESG scores and company profiles.

The data is pulled from Yahoo Finance , Marketwatch.com , Finviz.com and Macrotrends.com . The macrotrends scrape runs on Selenium and the website might sometimes fail to load. The function may just need to be re-run to work (assuming the ticker is available on the website). As a remedy it might sometimes help to set macrotrends().head = True which will then open a browser window while scraping the data.

• Returns a dataframe with income statements from either Macrotrends.com, Yahoo Finance or Marketwatch. Default source is 'macrotrends'.
• Class Arguments:
• ticker : valid company ticker
• source : 'yahoo', 'marketwatch', 'macrotrends', default: 'macrotrends'
• freq : 'A' (annual data), 'Q' (quarterly data), default: 'A'
• Returns a dataframe with balance sheets from either Macrotrends.com, Yahoo Finance or Marketwatch. Default source is 'macrotrends'.
• Class Arguments:
• ticker : valid company ticker
• source : 'yahoo', 'marketwatch', 'macrotrends', default: 'macrotrends'
• freq : 'A' (annual data), 'Q' (quarterly data), default: 'A'
• Returns a dataframe with cashflow statements from either Macrotrends.com, Yahoo Finance or Marketwatch. Default source is 'macrotrends'.
• Class Arguments:
• ticker : valid company ticker
• source : 'yahoo', 'marketwatch', 'macrotrends', default: 'macrotrends'
• freq : 'A' (annual data), 'Q' (quarterly data), default: 'A'
• Returns a dataframe with annual or quarterly financial ratios up to 2005 from Macrotrends.com.
• Class Arguments:
• ticker : valid company ticker
• source : choice has no effect, data is from Macrotrends.com
• freq : 'A' (annual data), 'Q' (quarterly data), default: 'A'
• Returns a dataframe with current key statistics and financial ratios from either Yahoo Finance or Finviz. Default key metrics for the 'macrotrends' and 'marketwatch' source is from Finviz.
• Class Arguments:
• ticker : valid company ticker
• source : 'yahoo', 'marketwatch', 'macrotrends', default: 'macrotrends'
• freq : choice has no effect, most recent data is returned

Yahoo Example <center><small><small>

payout_ratio profit_margin operating_margin_(ttm) return_on_assets_(ttm) return_on_equity_(ttm) .
0 0.2373 0.2133 0.2452 0.1312 0.6925 .

• Returns current earnings estimates for the current quarter, next quarter, current year and the next year from Yahoo Finance.
• Class Arguments:
• ticker : valid company ticker
• source : choice has no effect, data is from Yahoo Finance
• freq : choice has no effect, most recent data is returned
• Returns earnings estimates for the current quarter, next quarter, current year and the next year for the current date, 7 days ago, 30 days ago, 60 days ago and 90 days ago from Yahoo Finance.
• Class Arguments:
• ticker : valid company ticker
• source : choice has no effect, data is from Yahoo Finance
• freq : choice has no effect, most recent data is returned
• Returns earnings estimates and actual earnings for the past 4 quarters from Yahoo Finance.
• Class Arguments:
• ticker : valid company ticker
• source : choice has no effect, data is from Yahoo Finance
• freq : choice has no effect, most recent data is returned
• Returns revenue estimates for the current quarter, next quarter, current year and the next year from Yahoo Finance.
• Class Arguments:
• ticker : valid company ticker
• source : choice has no effect, data is from Yahoo Finance
• freq : choice has no effect, most recent data is returned
• Returns earnings estimates and actual earnings for the past 4 quarters from Yahoo Finance.
• Class Arguments:
• ticker : valid company ticker
• source : choice has no effect, data is from Yahoo Finance
• freq : choice has no effect, most recent data is returned

<center><small><small>

aapl industry sector(s) sandp_500
Current_Qtr. -0.079 nan nan nan
Next_Qtr. 0.088 nan nan nan
Current_Year 0.088 nan nan nan
Next_Year 0.195 nan nan nan
Next_5_Years_(per_annum) 0.1246 nan nan nan
Past_5_Years_(per_annum) 0.0842 nan nan nan

The earnings call transcripts are collected from The Motley Fool and are available until Q1 2018. The data returns a simple breakdown of the sections of the earnings call which will still need to be processed further. The full html of the call is also available.

• Returns recent history (up to Q1 2018) of earnings call transcripts.
• Function Arguments:
• html = True returns additional columns with html of transcript from Motley Fool.
• ticker : valid company ticker
• source : choice has no effect, data is the Motley Fool
• freq : choice has no effect
• Returns company insider transactions for the past year from Finviz.
• Class Arguments:
• ticker : valid company ticker
• source : choice has no effect, data is from Finviz
• freq : choice has no effect, most recent data is returned
• Returns recent history of analyst ratings from Finviz.
• Class Arguments:
• ticker : valid company ticker
• source : choice has no effect, data is from Finviz
• freq : choice has no effect, most recent data is returned

<center><small><small>

date action rating_institution rating price_target
2020-09-01 00:00:00 Reiterated JP Morgan Overweight $115 →$150
2020-09-01 00:00:00 Reiterated Cowen Outperform $530 →$133
2020-08-31 00:00:00 Reiterated Monness Crespi & Hardt Buy $117.50 →$144
2020-08-26 00:00:00 Reiterated Wedbush Outperform $515 →$600
2020-08-25 00:00:00 Reiterated Cowen Outperform $470 →$530
. . . . .

• Returns current ESG scores from Sustainalytics published on Yahoo Finance.
• Class Arguments:
• ticker : valid company ticker
• source : choice has no effect, data is from Yahoo Finance
• freq : choice has no effect, most recent data is returned
• Returns current corporate governance scores from Institutional Shareholder Services (ISS) published on Yahoo Finance.
• Class Arguments:
• ticker : valid company ticker
• source : choice has no effect, data is from Yahoo Finance
• freq : choice has no effect, most recent data is returned

<center><small><small>

audit board shareholder_rights compensation quality_score ticker date
0 1 1 1 3 1 AAPL 2020-08-25

• Returns company sector, industry, current number of employees and a company description.
• Class Arguments:
• ticker : valid company ticker
• source : choice has no effect, data is from Yahoo Finance
• freq : choice has no effect
• Returns current company executives with name, title, salary, age and their gender.
• Class Arguments:
• ticker : valid company ticker
• source : choice has no effect, data is from Yahoo Finance
• freq : choice has no effect

The functions below help to retrieve daily historical price data from Yahoo Finance as well as most recent option prices from Yahoo Finance or CBOE.