New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Documentation Fixes #2355
Documentation Fixes #2355
Conversation
@Tannmay Replace all other instances of query() -> search() too. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks @Tannmay. Just a couple of small changes to add.
@@ -315,7 +315,7 @@ files are downloaded. | |||
... vso.attrs.Time('2012-08-05 00:00:00', '2012-08-05 00:00:01'), | |||
... vso.attrs.Instrument('AIA')) # doctest: +REMOTE_DATA | |||
>>> len(database) # doctest: +SKIP | |||
37 | |||
70 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Notice that on the second paragraph below, it makes reference to the old value (37). Please, update it with the new on.
|
||
1 2011-06-07 06:33:02 ... 17.1 17.1 | ||
2 2011-06-07 06:33:03 ... 33.5 33.5 | ||
3 2011-06-07 06:33:29 ... 17.400000000000002 17.400000000000002 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
these entries defeat the purpose of showing a nice table. @Cadair, I would be happy for that to be truncated to onl y one decimal if shown in nm
. What do you think?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It is pretty ugly. Its why we should use perl.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
# doctest: +FLOAT_CMP
should make this cleaner?
37 2013-08-05 00:00:02 2013-08-05 00:00:03 AIA 33.5 33.5 N/A Yes | ||
4 2011-03-19 10:54:00 2011-03-19 10:54:00 AIA_3 17.1 17.1 spring No | ||
5 2014-04-09 06:00:12 2014-04-09 06:00:12 AIA_3 17.1 17.1 spring No | ||
id observation_time_start observation_time_end ... wavemax tags starred |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Why is truncating the results? is that because it's been run in a smaller window??
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I've run every code in Jupyter QT Console more than once,
every time the output was truncated. So may be it's because of smaller window itself.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Could you try to make it a larger window? I don't really understand why it is truncated. What's the point to choose the fields if then we don't see these?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This output is from pytest log I dump to a file.
You will have to rebase this with master after the last few PRs changed some of the same documentation files. Also if you have updated the numbers or the tables, can you please remove the #Skip flag so we can check it! |
Hello @Tannmay! Thanks for updating the PR.
Comment last updated on December 11, 2017 at 11:14 Hours UTC |
Doing the tests locally, I got a whole bunch of strange changes I had to make. Really unsure why, wondering if it could be my local ENV. Let us see if the online build passes. |
id observation_time_start ... wavemin wavemax | ||
--- ---------------------- ... ------------------ ------------------ | ||
1 2011-06-07 06:33:02 ... 17.1 17.1 | ||
2 2011-06-07 06:33:01 ... 13.100000000000001 13.100000000000001 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Which files are producing these long decimals? That's not good, we have to get showing a meaningful number, not the whole set of decimals.
Then I changed some of the tables for whitespace reasons. Hopefully nothing breaks
@Tannmay Thanks for the changes, the database doc file was a mess for a while now and I'm glad someone came along to deal with it for us! Hopefully we can see this into our next release (0.8.3) |
Inside sunpy/docs/guide/acquiring_data, document.rst and hek.rst has been
changed. The outputs were incorrect and missing in few sections which
have been corrected and search function is used in place or query.