Skip to content
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

Pdfmorph web-page #23

Open
wants to merge 24 commits into
base: source
Choose a base branch
from
Open

Conversation

RomanMatthew
Copy link

Copy link
Contributor

@sbillinge sbillinge left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

great job....

Is there a way to preview how it will look when it is built?

products/PDFmorph.rst Outdated Show resolved Hide resolved
products/PDFmorph.rst Outdated Show resolved Hide resolved
@RomanMatthew
Copy link
Author

@chiahaoliu @CJ-Wright @sbillinge Sorry to be tagging you guys so fervently in all this stuff but I just want to make sure that I did the right stuff. What do you think?

@CJ-Wright
Copy link
Member

@sbillinge if you look at the code there is a button on the file name line which looks like a document, that will render the rst to the best of its ability.

products/PDFmorph.rst Outdated Show resolved Hide resolved
products/PDFmorph.rst Outdated Show resolved Hide resolved
products/PDFmorph.rst Outdated Show resolved Hide resolved
products/PDFmorph.rst Outdated Show resolved Hide resolved
products/PDFmorph.rst Outdated Show resolved Hide resolved
independent way. The program was designed to help a researcher answer the question:
"has my material undergone a phase transition between these two measurements?"

PDFmorph makes use of several data manipulation techniques to correct for benign
Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@sbillinge I shortened the description a little bit here - please let me know if it's too detrimental to the content itself!

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It is good. Make sure there is a pointer to the user manual documentation

btw, please make an issue to check all the docstrings.

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

There's no manual in the diffpy.pdfmorph master, so I assume I'll have to link that once I make it, right? and will do on the docstrings issue! Would that be for this particular PR?

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

package specific doc should go to diffpy.pdfmorph repo in a different PR.

You will need to create a special branch named `gh-pages so github will build the website for you automatically. We can talk about more details in person.

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Sounds good! I'll grab you when you come back

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

package specific doc should go to diffpy.pdfmorph repo in a different PR.
You will need to create a special branch named `gh-pages so github will build the website for you automatically.

actually the best would be to publish package docs on readthedocs.io, for example the docs for diffpy.structure are at https://diffpystructure.readthedocs.io/en/stable.

I have a TODO issue #22 to stop hosting manual at the gh-pages branch and move it over to RTD. This should eventually happen for all diffpy packages.

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'll get started on that! Thank you @pavoljuhas. So publishing on rtd is what we would want to do for the documentation for all of diffpy? Sounds like a decent project!

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

So publishing on rtd is what we would want to do for the documentation for all of diffpy?

Yes, I think it would save a lot of work and keep the manuals in sync with the source code.

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@pavoljuhas would you mind providing the source for the diffpy.structure that was published on readthedocs? That would be really helpful, thanks!

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The RTD page is rebuild on pushes to https://github.com/diffpy/diffpy.structure repo with the manual sources in doc/manual. There is a small control file .readthedocs.yml to setup the manual compilation at RTD.

Setting up an RTD build for PDFmorph should be an issue in the pdfmorph project.
Here we should create documentation links pointing to the RTD pages - once they are up.

Copy link
Contributor

@sbillinge sbillinge left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

few small things

products/PDFmorph.rst Outdated Show resolved Hide resolved
products/PDFmorph.rst Outdated Show resolved Hide resolved
@pavoljuhas
Copy link
Member

I suggest to use lowercase filenames for the new pages.
This would make it easier to link them from other pages and less error prone to type the URL directly.

  • Please rename
products/PDFmorph.rst --> products/pdfmorph.rst
products/pdfmorphLICENSE.rst --> products/pdfmorph_license.rst
  • make clean html complains that pdfmorphlicense.rst is not included at all, please check
  • please link to the new pdfmorph page from _templates/menu01.html so we link it from the menu
  • whitespace - please fix issues reported from git diff --check source pdfmorph_web.
    Consider activating a commit hook that would prevent these in a first place:
    cd .git/hooks
    cp pre-commit.sample pre-commit

products/pdfmorph.rst Outdated Show resolved Hide resolved
products/pdfmorph.rst Outdated Show resolved Hide resolved
products/pdfmorph.rst Outdated Show resolved Hide resolved
products/pdfmorph.rst Outdated Show resolved Hide resolved
products/pdfmorph.rst Outdated Show resolved Hide resolved
products/pdfmorph.rst Show resolved Hide resolved
products/pdfmorph_license.rst Show resolved Hide resolved
@RomanMatthew
Copy link
Author

@pavoljuhas I fixed some of the problems but caused more in products/pythonpackages.rst. Could you help me figure out how to solve the issues I caused? I've been trying for a bit

@pavoljuhas
Copy link
Member

@RomanMatthew - I have fixed the conflicts by a temporary merge with the parent source branch.
Also there was an extra blank line in the table which broke the syntax.

I recommend to merge this PR using "Rebase and Merge" so it is easier to later on understand what changes it brings in.

@RomanMatthew
Copy link
Author

@pavoljuhas @sbillinge Does that mean that it should be ready to merge now?

@pavoljuhas
Copy link
Member

Does that mean that it should be ready to merge now?

Let me give it a quick read.

@pavoljuhas
Copy link
Member

BTW, we need to hold on with this merge until PDFmorph is really out.

Copy link
Contributor

@sbillinge sbillinge left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

few comments

products/pdfmorph.rst Outdated Show resolved Hide resolved
products/pdfmorph.rst Outdated Show resolved Hide resolved

conda create --name=<env_name> python=3

You can give the environment any name you like but it should
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

the python=3 ensures it will have python 3 installed so remove "but it should have some Python version 3 installed (though PDFmorph also works on Python 2.7)." This is just confusing.

Probably the best is at the top say "PDFmorph will run on python 3 and also python 2.7 or higher, but we recommend.....virtual environment. Here we give instructions for installing the python 3 version. With Anaconda...."

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I would suggest to drop instructions for creating new environment, it is not really needed as pdfmorph is quite lightweight package.

Perhaps the installation instructions should be

conda install --channel=diffpy diffpy.pdfmorph

or if you use conda-forge

conda install --channel=conda-forge diffpy.pdfmorph

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

its for novice users who are not familiar with conda. Maybe start this section out from right below the license information:

"PDFmorph is distribute and is best installed using conda. It should run in most python 3 conda environments and can be directly installed in an existing environment (using the commands listed below). If you do not currently have conda installed, here are some lightweight instructions for getting started:

  1. download and install Anaconda or mini-conda from continuum <https://www.continuum.io>__."
  2. create a python 3 environment with the command
conda create --name=<env_name> python=3

where you can give the environment any name you like.

You only need to create the environment once,
but every time you want to use PDFmorph you will have to
reactivate the environment in which it is installed by typing ::

...and so on

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Simon could you guve the new version a look?

products/pdfmorph.rst Outdated Show resolved Hide resolved
products/pdfmorph.rst Outdated Show resolved Hide resolved
@@ -0,0 +1,36 @@
This program is part of the DiffPy open-source project at Columbia
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Is it possible to connect directly to the license file in the package top level directory? This would be more robust/maintainable than having two license files hanging around. What if they are different? Which one is the correct one?

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Is it possible to connect directly to the license file in the package top level directory? This would be more robust/maintainable than having two license files hanging around. What if they are different?

For diffpy-cmi packages I use a dedicated license branch at
https://github.com/diffpy/diffpy-release/tree/license.
I make any text updates in the "license" branch and merge it to each package just before release, e.g., here.

Perhaps we could add a new license-pdfmorph branch to the "diffpy-release" repo and keep on merging it to this webpage sources and to the "diffpy.pdfmorph" master as well. If license files come from a common upstream branch, they will stay in sync.

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

is this something that would be top-priority upon release?

Copy link
Contributor

@sbillinge sbillinge left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

yes, these changes are all good. @pavoljuhas, waiting for your approval on this.

Include only when used.
Fix issues from `git diff --check`.
List compatible Python versions.
Suggest pip rather than easy_install.
@pavoljuhas
Copy link
Member

Here is my take on that page - RomanMatthew/diffpy.github.io@pdfmorph_web...pavoljuhas:pdfmorph_web_pj
and here is the page rendered - http://pavoljuhas.github.io/diffpy.github.io/products/pdfmorph.html.

If that looks OK, please pull

git pull https://github.com/pavoljuhas/diffpy.github.io.git pdfmorph_web_pj

@RomanMatthew
Copy link
Author

@pavoljuhas The changes should be implemented now!

Copy link
Member

@pavoljuhas pavoljuhas left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This looks good to me, but let's hold on with publishing until the release is out.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants