Skip to content
This repository was archived by the owner on Jul 28, 2025. It is now read-only.

Duplicate layers#60

Merged
arnaudon merged 10 commits intomainfrom
spaces
Sep 22, 2022
Merged

Duplicate layers#60
arnaudon merged 10 commits intomainfrom
spaces

Conversation

@arnaudon
Copy link
Copy Markdown
Collaborator

No description provided.

@codecov
Copy link
Copy Markdown

codecov bot commented Sep 20, 2022

Codecov Report

Merging #60 (aaba032) into main (6a957c8) will decrease coverage by 0.22%.
The diff coverage is 81.63%.

@@            Coverage Diff             @@
##             main      #60      +/-   ##
==========================================
- Coverage   86.25%   86.03%   -0.23%     
==========================================
  Files          14       14              
  Lines        1579     1611      +32     
  Branches      251      258       +7     
==========================================
+ Hits         1362     1386      +24     
- Misses        136      141       +5     
- Partials       81       84       +3     
Flag Coverage Δ
pytest 86.03% <81.63%> (-0.23%) ⬇️

Flags with carried forward coverage won't be shown. Click here to find out more.

Impacted Files Coverage Δ
src/morphology_workflows/repair.py 79.31% <81.25%> (-0.69%) ⬇️
src/morphology_workflows/tasks/repair.py 100.00% <100.00%> (ø)

arnaudon added 2 commits September 20, 2022 18:15
@arnaudon
Copy link
Copy Markdown
Collaborator Author

@adrien-berchet , in the last commit, I try to save the df with extra duplicated rows, with ValidationResultSet, but it does not seem to work. Do you have an idea how to do?

@arnaudon
Copy link
Copy Markdown
Collaborator Author

and if possible of course

@adrien-berchet
Copy link
Copy Markdown
Member

What do you mean by "not work"?

@arnaudon
Copy link
Copy Markdown
Collaborator Author

Something is a little weird, the df needs to be modified in place, even if I return the ValidationResultSet.
Also, if I change the df size in place, it crashes dvf, you even have put a raise to prevent bad crash, so I had to trick things here a little.

@adrien-berchet
Copy link
Copy Markdown
Member

Ah yeah, remember that the philosophy of DVF is to validate existing data, not creating new data. For example in the cloning step we don't add the clones in the DF, we only add them in the neurondb file. If you want to create new data you could create a column containing a list of the results that were created from the current row for example.

@arnaudon
Copy link
Copy Markdown
Collaborator Author

yep, so let's do something like I did here, let me know if it's good, so we can merge and update clone the same way (I created MR for it already)

@arnaudon
Copy link
Copy Markdown
Collaborator Author

@adrien-berchet , this does not work, as there is a loop over extensions, and we do several times the iterrows over the df_tmp, which does not have the values for previous extensions...

@arnaudon
Copy link
Copy Markdown
Collaborator Author

ok, now it works, it's not very clean, but it's fine for now, unless you want to try to improve

@arnaudon arnaudon merged commit 54cdf94 into main Sep 22, 2022
@arnaudon arnaudon deleted the spaces branch September 22, 2022 09:25
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants