data-analysis

PR #22722 introduced a common method for the validation of the parameters of an estimator. We now need to use it in all estimators.

Please open one PR per estimator or family of estimators (if one inherits from another). The title of the PR should mention which estimator it's dealing with and the description of the PR should begin with towards #23462.

Steps

• The estimator must define

The Mixed Time-Series chart type allows for configuring the title of the primary and the secondary y-axis.
However, while only the title of the primary axis is shown next to the axis, the title of the secondary one is placed at the upper end of the axis where it gets hidden by bar values and zoom controls.

How to reproduce the bug

1. Create a mixed time-series chart
2. Configure axi

Pandas version checks

• I have checked that the issue still exists on the latest versions of the docs on main here

Location of the documentation

https://pandas.pydata.org/docs/reference/api/pandas.DataFrame.to_excel.html

Documentation problem

It is not a "problem" but enhancement.

Suggested fix for documentation

Do suggest the [S

Problem

See #3856 . Developer would like the ability to configure whether the developer menu or viewer menu is displayed while they are developing on cloud IDEs like Gitpod or Github Codespaces

Solution

Create a config option

showDeveloperMenu: true | false | auto

where

• true: always shows the developer menu locally and while deployed
• false: always sho

Is your feature request related to a problem? Please describe.
When working with a big piece of text, I sometimes scroll down and copy some text into another tab. When switching back to the first tab, both the input and the output pane is back on top. So I don't know where I was working just now.

Describe the solution you'd like
After tab switching, scroll position should be remembere

• Base README.md
• Quizzes
• Introduction base README
  • Defining Data Science README
  • Defining Data Science assignment
  • Ethics README
  • Ethics assignment
  • Defining Data README
  • Defining Data assignment
  • Stats and Probability README
  • Stats and Probability assignment
• Working with Data base README
  • Rel

It is a bit confusing when someone imports a file or pastes from clipboard and wants to enable column headers.
The wording that we chose "Parse next" isn't quite what we meant as "Parse first".
We have several translation files that likely need to be updated.
For example, the EN translation:
https://github.com/OpenRefine/OpenRefine/blob/3cbb5b143df3caa6e50d5493a34cee3f12cbcf77/extensions/dat

Describe the bug

Flag can not create an appropriate CSV file when the interface have a textbox / text which includes a comma .
The CSV file columns are incorrectly created assuming the comma in the text box is a separator.
See the attached screenshots.

Thank you!

Is there an existing issue for this?

• I have searched the existing issues

Reproduction

kmkarakaya/Auto_Rev

Collection of follow-ups to #5827. These can/should be broken out into individual PRs. Many are relatively straightforward and would make a good first PR.

General

• Documentation (none was added in original PR).
• Release notes.
• Example notebook.
• Double-check how sm.tsa.arima.ARIMA works with fix_params (it should fail except when the fit method is statespace

See:
gonum/gonum#845 (comment)

For the autoencoder in pyod, how do I adjust the learning rate?

numpydoc supports docstring validation that we should enable to supplement things like pydocstyle checks. The numpydoc validation will help us with more semantic checking, such as ensuring that docstrings actually align with the function signatures that they are attached to.