- https://github.com/Benjamin-Loison
- Joined on
2022-10-16
Block a user
Benjamin_Loison
commented on issue Benjamin_Loison/Robust_image_source_identifica…#21
2024-03-26 01:39:06 +01:00
Estimating PRNU on Gaussian noise images
plt.title('Actual PRNU')
plt.imshow(prnus[0])
plt.show()
image = np.array(imagesWithPrnu[0][:1]).mean(axis = 0)
plt.title(f'First image with PRNU\ni.e. estimated PRNU\nRMS…
Benjamin_Loison
commented on issue Benjamin_Loison/Robust_image_source_identifica…#21
2024-03-26 01:24:31 +01:00
Estimating PRNU on Gaussian noise images
Could render intermediary image differences, as it is easy to see an almost black uniform image but it is hard to compare 2 random images. However, this assumes that the color scale for each image…
Benjamin_Loison
commented on issue Benjamin_Loison/Robust_image_source_identifica…#21
2024-03-25 20:46:39 +01:00
Estimating PRNU on Gaussian noise images
Showcase an example and now make a curve to make it clearer. Note that if want a maximum precision curve, may have to pay attention to complexity.
Benjamin_Loison
pushed to master at Benjamin_Loison/Robust_image_source_identifica…
2024-03-25 20:14:35 +01:00
Benjamin_Loison
pushed to master at Benjamin_Loison/Robust_image_source_identifica…
2024-03-25 20:01:54 +01:00
Benjamin_Loison
pushed to master at Benjamin_Loison/Robust_image_source_identifica…
2024-03-25 19:46:46 +01:00
ValueError: image has wrong mode
on ImageChops.difference
with mode
F
Benjamin_Loison
pushed to master at Benjamin_Loison/Robust_image_source_identifica…
2024-03-25 18:37:14 +01:00
Benjamin_Loison
opened issue Benjamin_Loison/Robust_image_source_identifica…#22
2024-03-25 18:13:38 +01:00
Track:
Benjamin_Loison
opened issue Benjamin_Loison/Robust_image_source_identifica…#21
2024-03-25 18:01:00 +01:00
Estimating PRNU on Gaussian noise images
Benjamin_Loison
pushed to master at Benjamin_Loison/Robust_image_source_identifica…
2024-03-25 17:45:04 +01:00
malformed module path "nginx-formatter": missing dot in first path element
on go install nginx-formatter@latest
upstream sent too big header while reading response header from upstream
how to determine required limits if any help?
The Stack Overflow answer 25762701 seems to solve the issue.
upstream sent too big header while reading response header from upstream
how to determine required limits if any help?
upstream sent too big header while reading response header from upstream
how to determine required limits if any help?
david-lev fork
Get with and without -s
:
pipenv run python download.py fr.gouv.franceidentite
24/03/2024 15:20:14> [ERROR][playstore.playstore.Playstore][_download_with_progress()]…
Not considering correctly escaped spaces with <kbd>tab</kbd>
david-lev fork