Comments (4)
Hi @JohannaRahm, have you noticed the cropping issue happening in both 2D and 2.5D models, or have you only tried 2D model inference?
I cannot find anywhere in the inference pipeline where we hard-code a 2048 pixel limit. In your configuration files, have you changed the "dataset->height" and "dataset->width" parameters to 2562?
from microdl.
I created an example with our models to make it easier to find the error. The inference data contains 3 FOV with size 2048x2048, 2000x2000, and 1000x1000. They are cropped to 2048x2048, 1024x1024, and 512x512 respectively.
Here the paths:
- inference yml file
/hpc/projects/comp_micro/projects/virtualstaining/2022_microDL_nuc_mem/configfiles/tests/input_size/config_inference_2022_03_15_nuc_mem_heavy_augmentation_test_input_size.yml
- inference data
/hpc/projects/comp_micro/projects/HEK/2022_04_19_nuc_mem_LF_63x_04NA/all_pos_single_page/test_different_input_size/
- inference results
/hpc/projects/comp_micro/projects/virtualstaining/2022_microDL_nuc_mem/models/2022_03_15_nuc_mem/loss_functions/heavy_augmentation_z25-60_mae/pred_input_size/
- model dir
/hpc/projects/comp_micro/projects/virtualstaining/2022_microDL_nuc_mem/models/2022_03_15_nuc_mem/loss_functions/heavy_augmentation_z25-60_mae/
- model yml file
/hpc/projects/comp_micro/projects/virtualstaining/2022_microDL_nuc_mem/configfiles/input_nuc_mem/loss_functions/config_train_2022_03_15_nuc_mem_heavy_augmentation_z25-60_mae.yml
- preprocess directory
/hpc/projects/comp_micro/projects/virtualstaining/2022_microDL_nuc_mem/preprocess/2022_03_15_nuc_mem_z25-60/
- preprocess yml file
/hpc/projects/comp_micro/projects/virtualstaining/2022_microDL_nuc_mem/preprocess/config_preprocess_2022_03_15_nuc_mem_z25-60.yml
The width and height of the inferred data are not specified and in the scenario posted above the sizes of images in the inference data slightly differs, which make specification not possible. Looking at the sizes of the inferred images, they seem to be cropped to something which is dividable by tile size (256x256). Is specification of inference size a must and if yes why and where? The only width and height defined in the yml files are the tile sizes.
I have only tried 2D model inference.
In this test the inference code from this PR #155 is used, but the test above showed that this unexpected behavior also occurs in commit 151cc25 master branch.
from microdl.
Update: The pixel values are correctly presented in microDL. Fiji shows two versions of pixel values for these images -> see screenshot with example value = 83 (32851), where 32851 is the value stored in the pixel - rightly captured by microDL.
from microdl.
I have the same issue as @JohannaRahm with the inference images produced by microDL. The 2012x2012 input images (images resized on x-y registration) used for microDL inference produces 1024x1024 output images. The central 1024x1024 pixels in the image are chosen to run the inference.
from microdl.
Related Issues (20)
- Config issues on gunpowder dataloading branch HOT 12
- Flatfielding computation error on gunpowder dataloading branch HOT 2
- Improve masking of fluorescence data in preprocessing HOT 2
- configs should use channel names and not channel index HOT 2
- Metadata Structure HOT 2
- z-score HOT 1
- Inference shouldn't use gunpowder HOT 5
- intensity.csv HOT 1
- Convert existing tensorflow models to pytorch HOT 3
- Does inference need its own config file? HOT 1
- data problem HOT 3
- Make model architecture compatible with deployment HOT 9
- Training error without augmentation HOT 1
- Training on gpu-c-1 scratch space HOT 7
- Normalization statistics don't need to be stored with additional key HOT 1
- Unexpected behavior in model batch prediction? HOT 8
- Runtime error testing lightning pipeline HOT 5
- unify preprocessing CLI with lightning CLI HOT 1
- Brain_2.5DUNet HOT 4
- Paper Figure 5. HOT 3
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from microdl.