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

Generative rotated molecules from a finite set of particules #2

Merged
merged 7 commits into from
Jul 31, 2021

Conversation

NicolasLegendre1
Copy link
Contributor

No description provided.

Copy link
Contributor

@ninamiolane ninamiolane left a comment

Choose a reason for hiding this comment

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

Looking good!! Thanks @NicolasLegendre1 . I've left a few comments.

sim_volumes.py Outdated Show resolved Hide resolved

def get_random_quat(num_pts):
"""Generate a list of quaternions by using uniform distribution.

Copy link
Contributor

Choose a reason for hiding this comment

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

How do you know this samples from a uniform distribution, do you have a reference (Wikipedia, research paper) that explains why these formulas work?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

okay I will add that but i'm not sure how to present that into the Docstring of the function

sim_volumes.py Outdated Show resolved Hide resolved
sim_volumes.py Outdated Show resolved Hide resolved
sim_volumes.py Outdated Show resolved Hide resolved
sim_volumes.py Outdated Show resolved Hide resolved
sim_volumes.py Outdated Show resolved Hide resolved
sim_volumes.py Outdated Show resolved Hide resolved
sim_volumes.py Outdated Show resolved Hide resolved
volume = np.zeros((vol_size,) * 3)
volume = sim_volumes.modify_weight(points, volume, vol_size, center)
assert volume.shape == (vol_size,) * 3
assert volume[1][1][1] == 3.4866983294215885e-164
Copy link
Contributor

Choose a reason for hiding this comment

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

How did you get this value?

If you run sim_volumes.modify_weight on your computer and then copy-pasted it here, it's slightly less effective as a unit-test (it's still useful, as it protects your code from being modified by other contributors).

Is there a simpler test (with a simpler volume) that could be run here, so that the volume[1][1][1] can be computed manually - so that the manual computation is the check for the modify_weight's computation?

@ninamiolane
Copy link
Contributor

@NicolasLegendre1 you can ignore the DeepSource errors.

@fredericpoitevin could you make deepsource automatically ignore the above errors (see my comment in PR compSPI/ioSPI#14)? There's no hurry though, we can merge the PRs with DeepSource failing.

Also, it seems that the DeepSource transformers have been run on this PR, as opposed to PR compSPI/ioSPI#14 !

The difference between this PR and the PR#14 from ioSPI is that PR#14 comes from the branch on Nicolas's fork, and this PR is directly on a branch on the main repo. In order for the DeepSource transformers to run on your PR#14, Nicolas you will need to enable DeepSource on your own ioSPI repo.

@fredericpoitevin
Copy link
Member

@NicolasLegendre1 you can ignore the DeepSource errors.

@fredericpoitevin could you make deepsource automatically ignore the above errors (see my comment in PR compSPI/ioSPI#14)? There's no hurry though, we can merge the PRs with DeepSource failing.

Also, it seems that the DeepSource transformers have been run on this PR, as opposed to PR compSPI/ioSPI#14 !

The difference between this PR and the PR#14 from ioSPI is that PR#14 comes from the branch on Nicolas's fork, and this PR is directly on a branch on the main repo. In order for the DeepSource transformers to run on your PR#14, Nicolas you will need to enable DeepSource on your own ioSPI repo.

Thanks @NicolasLegendre1 and @ninamiolane!
I did add the "ignore rule" but I think we should merge regardless. Once merged, I'll create a tests/ directory and move the test files there - this way we have the same structure across all compSPI repos and also the same deepsource setup.

@ninamiolane
Copy link
Contributor

@fredericpoitevin @NicolasLegendre1 deep sources errors are ignored! Ready to merge once the comments are addressed 🎉

Copy link
Contributor

@ninamiolane ninamiolane left a comment

Choose a reason for hiding this comment

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

@NicolasLegendre1 @fredericpoitevin LGTM! (I've seen a few other details, but in the interest of merging PRs slightly faster I am OK to merge now 🤗 ). Should we contact Youssef or Julien to officially merge here?

@fredericpoitevin
Copy link
Member

@NicolasLegendre1 @fredericpoitevin LGTM! (I've seen a few other details, but in the interest of merging PRs slightly faster I am OK to merge now 🤗 ). Should we contact Youssef or Julien to officially merge here

Let's merge this PR now. I'd like to homogenize the structure across compSPI repos before soliciting maintainers: what do you think?

@fredericpoitevin fredericpoitevin merged commit 6b14bad into master Jul 31, 2021
thisFreya added a commit that referenced this pull request Nov 6, 2021
Merging Arjun's branch into wrapper-function-headers
geoffwoollard added a commit that referenced this pull request Feb 18, 2022
merge compSPI/simSPI:master into geoffwoollard/simSPI:multisclice_compspifft
@fredericpoitevin fredericpoitevin deleted the nicolas branch April 13, 2022 15:55
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.

3 participants