Introduce order for pixel extraction #2602

Ivanidzo4ka · 2019-02-18T23:06:49Z

Ivanidzo4ka · 2019-02-18T23:07:24Z

src/Microsoft.ML.ImageAnalytics/ExtensionsCatalog.cs

-        /// <param name="interleave">Wheather to interleave the pixels, meaning keep them in the `ARGB ARGB` order, or leave them separated in the planar form, where the colors are outputed one by one
-        /// alpha, red, green, blue for all the pixels of the image. </param>
+        /// <param name="colors">What colors to extract.</param>
+        /// <param name="order">In which order extract channels from pixel.</param>


colors #Closed

Ivanidzo4ka · 2019-02-18T23:09:13Z

src/Microsoft.ML.ImageAnalytics/ImagePixelExtractor.cs

+            [Argument(ArgumentType.AtMostOnce, HelpText = "Order of colors.")]
+            public ImagePixelExtractingEstimator.ColorsOrder Order = Defaults.Order;
+
+            [Argument(ArgumentType.AtMostOnce, HelpText = "Whether to separate each channel or interleave in specified order", ShortName = "interleave")]
            public bool InterleaveArgb = Defaults.Interleave;


InterleaveArgb [](start = 24, length = 14)

change to interleave since it's no longer argb #Resolved

codecov · 2019-02-19T02:51:56Z

Codecov Report

❗ No coverage uploaded for pull request base (master@f063510). Click here to learn what that means.
The diff coverage is 87.54%.

@@            Coverage Diff            @@
##             master    #2602   +/-   ##
=========================================
  Coverage          ?   71.66%           
=========================================
  Files             ?      804           
  Lines             ?   141988           
  Branches          ?    16127           
=========================================
  Hits              ?   101751           
  Misses            ?    35795           
  Partials          ?     4442

Flag	Coverage Δ
#Debug	`71.66% <87.54%> (?)`
#production	`67.96% <83.68%> (?)`
#test	`85.75% <97.33%> (?)`

Impacted Files	Coverage Δ
...c/Microsoft.ML.StaticPipe/ImageTransformsStatic.cs	`95.5% <ø> (ø)`
...osoft.ML.OnnxTransformerTest/OnnxTransformTests.cs	`98.52% <100%> (ø)`
...est/Microsoft.ML.Tests/TensorFlowEstimatorTests.cs	`98.2% <100%> (ø)`
...t.ML.OnnxTransformerTest/DnnImageFeaturizerTest.cs	`97.36% <100%> (ø)`
src/Microsoft.ML.ImageAnalytics/ImageResizer.cs	`84.64% <100%> (ø)`
src/Microsoft.ML.StaticPipe/ImageStaticPipe.cs	`54.54% <50%> (ø)`
...c/Microsoft.ML.ImageAnalytics/ExtensionsCatalog.cs	`37.5% <50%> (ø)`
...rosoft.ML.ImageAnalytics/VectorToImageTransform.cs	`72.23% <80.85%> (ø)`
...Microsoft.ML.ImageAnalytics/ImagePixelExtractor.cs	`82.55% <87.5%> (ø)`
test/Microsoft.ML.Tests/ImagesTests.cs	`98.85% <97.18%> (ø)`

Ivanidzo4ka · 2019-02-22T19:31:48Z

src/Microsoft.ML.ImageAnalytics/ExtensionsCatalog.cs

-        /// <param name="interleave">Whether the pixels are interleaved, meaning whether they are in `ARGB ARGB` order, or separated in the planar form, where the colors are specified one by one
+        /// <param name="colors"> Specifies which <see cref="ImagePixelExtractingEstimator.ColorBits"/> are in the input pixel vectors. The order of colors specified in <paramref name="order"/></param>
+        /// <param name="order">In which order extract colors presented in array.</param>
+        /// <param name="interleave">Whether the pixels are interleaved, meaning whether they are in <paramref name="order"/> order, or separated in the planar form, where the colors are specified one by one
        /// alpha, red, green, blue for all the pixels of the image. </param>
        /// <param name="scale">The values are scaled by this value before being converted to pixels.</param>
        /// <param name="offset">The offset is subtracted (before scaling) before converting the values to pixels.</param>


change it #Closed

Ivanidzo4ka · 2019-02-22T19:32:15Z

src/Microsoft.ML.ImageAnalytics/ExtensionsCatalog.cs

-        /// <param name="interleave">Whether the pixels are interleaved, meaning whether they are in `ARGB ARGB` order, or separated in the planar form, where the colors are specified one by one
+        /// <param name="colors"> Specifies which <see cref="ImagePixelExtractingEstimator.ColorBits"/> are in the input pixel vectors. The order of colors specified in <paramref name="order"/></param>
+        /// <param name="order">In which order extract colors presented in array.</param>
+        /// <param name="interleave">Whether the pixels are interleaved, meaning whether they are in <paramref name="order"/> order, or separated in the planar form, where the colors are specified one by one


pixels [](start = 49, length = 6)

colors #Closed

artidoro · 2019-02-22T22:58:01Z

src/Microsoft.ML.ImageAnalytics/ExtensionsCatalog.cs

-        /// <param name="offset">Offset color pixel value by this amount.</param>
-        /// <param name="asFloat">Output the array as float array. If false, output as byte array.</param>
+        /// <param name="colors">What colors to extract.</param>
+        /// <param name="order">In which order extract colors from pixel.</param>


In which order extract colors from pixel. [](start = 32, length = 41)

Would suggest:
In which order to extract colors from pixel.

(Same for the other extension) #Resolved

artidoro · 2019-02-22T23:04:21Z

src/Microsoft.ML.ImageAnalytics/ExtensionsCatalog.cs

+        /// <param name="colors">What colors to extract.</param>
+        /// <param name="order">In which order extract colors from pixel.</param>
+        /// <param name="interleave">Whether to interleave the pixels colors, meaning keep them in the <paramref name="order"/> order, or leave them in the plannar form:
+        /// first output one color values for all pixels, then another color and so on.</param>


one color values for all pixels [](start = 25, length = 31)

Maybe: "all the values for one color for all pixels, then all the values for another color and so on." #Resolved

artidoro · 2019-02-22T23:09:02Z

src/Microsoft.ML.ImageAnalytics/ExtensionsCatalog.cs

+        /// <param name="colors"> Specifies which <see cref="ImagePixelExtractingEstimator.ColorBits"/> are in the input pixel vectors. The order of colors specified in <paramref name="order"/></param>
+        /// <param name="order">In which order extract colors presented in array.</param>
+        /// <param name="interleave">Whether the pixels are interleaved, meaning whether they are in <paramref name="order"/> order, or separated in the planar form, where the colors are specified one by one
+        /// for all the pixels of the image. </param>


Could you make this description and the one in the extension above one consistent?

artidoro · 2019-02-22T23:11:39Z

src/Microsoft.ML.ImageAnalytics/ImagePixelExtractor.cs

@@ -85,7 +88,7 @@ internal bool TryUnparse(StringBuilder sb)
            {
                Contracts.AssertValue(sb);
                if (UseAlpha != null || UseRed != null || UseGreen != null || UseBlue != null || Convert != null ||
-                    Offset != null || Scale != null || InterleaveArgb != null)
+                    Offset != null || Scale != null || Interleave != null)


Why do you not need to add Order != null here? #Resolved

zeahmed · 2019-02-22T23:23:07Z

src/Microsoft.ML.ImageAnalytics/VectorToImageTransform.cs

        /// <param name="outputColumnName">Name of the column resulting from the transformation of <paramref name="inputColumnName"/>. Null means <paramref name="inputColumnName"/> is replaced.</param>
        /// <param name="inputColumnName">Name of the input column.</param>
        /// <param name="colors">What colors to extract.</param>
-        /// <param name="interleave">Whether to interleave the pixels, meaning keep them in the `RGB RGB` order, or leave them in the plannar form: of all red pixels,
-        /// than all green, than all blue.</param>
+        /// <param name="order">In which order extract colors presented in array.</param>


extract [](start = 47, length = 7)

extracted? #Closed

zeahmed · 2019-02-22T23:27:13Z

src/Microsoft.ML.ImageAnalytics/ExtensionsCatalog.cs

@@ -150,16 +152,26 @@ public static VectorToImageConvertingEstimator ConvertToImage(this TransformsCat
        /// <param name="width">The width of the output images.</param>
        /// <param name="outputColumnName"> Name of the column resulting from the transformation of <paramref name="inputColumnName"/>.</param>
        /// <param name="inputColumnName"> Name of column to transform. If set to <see langword="null"/>, the value of the <paramref name="outputColumnName"/> will be used as source.</param>
-        /// <param name="colors"> Specifies which <see cref="ImagePixelExtractingEstimator.ColorBits"/> are in the input pixel vectors. The order of colors is: Alpha, Red, Green Blue.</param>
-        /// <param name="interleave">Whether the pixels are interleaved, meaning whether they are in `ARGB ARGB` order, or separated in the planar form, where the colors are specified one by one
+        /// <param name="colors"> Specifies which <see cref="ImagePixelExtractingEstimator.ColorBits"/> are in the input pixel vectors. The order of colors specified in <paramref name="order"/></param>


< [](start = 192, length = 2)

period at the end. #Closed

artidoro · 2019-02-22T23:27:19Z

src/Microsoft.ML.ImageAnalytics/ImagePixelExtractor.cs

-                                        if (g) { vf[idst++] = (pb.G - offset) * scale; }
-                                        if (b) { vf[idst++] = (pb.B - offset) * scale; }
+
+                                        if (a != -1) { vf[idst + a] = (pb.A - offset) * scale; }


nit: extra line. #Resolved

zeahmed · 2019-02-22T23:31:01Z

I don't see any test for extracting pixels in different color order. Do you have that? #Closed

artidoro · 2019-02-22T23:49:22Z

            int height = ex.Interleave ? dims[0] : dims[1];

Not a blocking comment, but it would be very useful for future contributions to this code to know what planes represents. If you could add a line of comment on that it would be great.

Refers to: src/Microsoft.ML.ImageAnalytics/ImagePixelExtractor.cs:325 in cee009e. [](commit_id = cee009e, deletion_comment = False)

artidoro · 2019-02-22T23:58:43Z

src/Microsoft.ML.ImageAnalytics/ImagePixelExtractor.cs

                                if (!vb.IsEmpty)
                                {
-                                    for (int x = 0; x < w; x++, idstBase++)
+                                    for (int x = 0; x < w; x++, idst++)
                                    {


If you refactor this by having the if...else if...else loop inside the for loop you can simplify the code a bit. It would look like:
for... { var pb = src.GetPixel(x,y); if... else if... else... } #Resolved

artidoro · 2019-02-23T00:01:28Z

src/Microsoft.ML.ImageAnalytics/ImagePixelExtractor.cs

            public readonly float Scale;

-            /// <summary> Whether to interleave the pixels, meaning keep them in the `ARGB ARGB` order, or leave them separated in the plannar form.</summary>
+            /// <summary>Whether to interleave the pixels colors, meaning keep them in the <see cref="Order"/> order, or leave them in the plannar form.</summary>


Whether to interleave the pixels colors, meaning keep them in the order, or leave them in the plannar form. [](start = 25, length = 127)

Could you double check with the catalog to make sure we have something consistent for this line? #Resolved

artidoro · 2019-02-23T00:06:43Z

src/Microsoft.ML.ImageAnalytics/ImagePixelExtractor.cs

+            float scale = Defaults.Scale,
+            bool asFloat = Defaults.Convert)
+            : base(Contracts.CheckRef(env, nameof(env)).Register(nameof(ImagePixelExtractingEstimator)),
+                  new ImagePixelExtractingTransformer(env, outputColumnName, inputColumnName, colors, order, interleave,  offset, scale, asFloat))


[](start = 120, length = 2)

nit: two spaces. #Resolved

artidoro · 2019-02-23T00:08:33Z

src/Microsoft.ML.ImageAnalytics/VectorToImageTransform.cs

@@ -84,33 +99,37 @@ internal bool TryUnparse(StringBuilder sb)
            {
                Contracts.AssertValue(sb);
                if (ContainsAlpha != null || ContainsRed != null || ContainsGreen != null || ContainsBlue != null || ImageWidth != null ||
-                    ImageHeight != null || Offset != null || Scale != null || InterleaveArgb != null)
+                    ImageHeight != null || Offset != null || Scale != null || Interleave != null || Order != null || DefaultAlpha != null ||
+                    DefaultBlue != null || DefaultGreen != null || DefaultRed != null)


Order? #Closed

What Order?

In reply to: 259549474 [](ancestors = 259549474)

Sorry I saw you added it :)

In reply to: 259549716 [](ancestors = 259549716,259549474)

artidoro · 2019-02-23T00:13:38Z

src/Microsoft.ML.ImageAnalytics/ExtensionsCatalog.cs

        /// <param name="scale">The values are scaled by this value before being converted to pixels.</param>
        /// <param name="offset">The offset is subtracted (before scaling) before converting the values to pixels.</param>
+        /// <param name="defaultAlpha">Default value for alpha color, would be overriden if <paramref name="colors"/> contains <see cref="ImagePixelExtractingEstimator.ColorBits.Alpha"/>.</param>


I think your code now has the opposite logic.

Would prefer to be consistent with the above extension here too. If you could also reorder them so that the first one applied comes first that would be great. #Resolved

What do you mean?

In reply to: 259550143 [](ancestors = 259550143)

Are you talking about scale offset or defaultAlpha?

In reply to: 259550340 [](ancestors = 259550340,259550143)

Sorry I think codeflow did not pick up the right location for this. I meant to comment on scale and offset.

I think the arguments should be presented in the same order in which they are applied.

I think the order and the comment should match the above extension for ImageLoader

I think the logic that you have in your code here does not match the comment:

machinelearning/src/Microsoft.ML.ImageAnalytics/VectorToImageTransform.cs

Lines 415 to 419 in cee009e

pixel = Color.FromArgb(

ex.Alpha ? (int)Math.Round(alpha * scale - offset) : 0,

(int)Math.Round(red * scale - offset),

(int)Math.Round(green * scale - offset),

(int)Math.Round(blue * scale - offset));

It seems that you are first scaling and the applying the offset. #Resolved

So I can do this: P-pixel x -VectorValue
p= xscale1-offset1
x =pscale2-offset2

this way I need to solve equation in order to pick up scale1 and offset1 if I know scale2 and offset2.
or I can have

x=(p-offset1)scale1
p = xscale2 - offset2
and relationship between offset1 = -offset2 and scale1 = 1/scale2

So in one transform i apply scale first, in another i apply offset.
I can make them same order in their parameters, but since I'm specifying which applied first and which second, it looks weird then you put one which applied second to first in argument list.

In reply to: 259551787 [](ancestors = 259551787)

Thank you for explaining the logic it makes sense like this!

In reply to: 259553517 [](ancestors = 259553517,259551787)

artidoro · 2019-02-23T00:16:12Z

test/Microsoft.ML.Tests/ImagesTests.cs

-            var pixels = new ImagePixelExtractingTransformer(env, "ImagePixels", "ImageCropped", ImagePixelExtractingEstimator.ColorBits.All, true, 2f / 255, 127.5f).Transform(cropped);
-            IDataView backToBitmaps = new VectorToImageConvertingTransformer(env, "ImageRestored", "ImagePixels",
-                imageHeight, imageWidth, ImagePixelExtractingEstimator.ColorBits.All, true, 255f / 2, -1f).Transform(pixels);
+            var pixels = new ImagePixelExtractingTransformer(env, "ImagePixels", "ImageCropped", ImagePixelExtractingEstimator.ColorBits.All, interleave: true, scale: 2f/19, offset: 30).Transform(cropped);


cale: 2f/19, offset: 30) [](start = 161, length = 24)

why are the scale and offset changing?

It was hard to test. all first pixels are white which is 255 in each channel. (255-127.5)*(2/255) = 1.
And I didn't like old vector to image logic of scaling.
which was (pixel -offset)*scale.
Since this two transforms are tangle up together i prefer scale in PixelExtraction would be 1/scale in VectorToImage, and offset = -offset.
This way they opposite.

In reply to: 259550473 [](ancestors = 259550473)

Ivanidzo4ka · 2019-02-23T00:56:34Z

            int height = ex.Interleave ? dims[0] : dims[1];

you mean planes from above?
It just how many channels you extract from your image.

In reply to: 466587738 [](ancestors = 466587738)

Refers to: src/Microsoft.ML.ImageAnalytics/ImagePixelExtractor.cs:325 in cee009e. [](commit_id = cee009e, deletion_comment = False)

zeahmed

Looks good to me. Thanks for doing it.

artidoro · 2019-02-23T01:15:43Z

    /// </summary>

Could you add a remarks section where you write the scaling equation that you wrote bellow?

Refers to: src/Microsoft.ML.ImageAnalytics/ExtensionsCatalog.cs:149 in 7e0140b. [](commit_id = 7e0140b, deletion_comment = False)

artidoro · 2019-02-23T01:16:20Z

    /// </summary>

Same here could you add the equation for scaling to the remarks section?

Refers to: src/Microsoft.ML.ImageAnalytics/ExtensionsCatalog.cs:26 in 7e0140b. [](commit_id = 7e0140b, deletion_comment = False)

artidoro

Thank you Ivan! It's great to see the new feature and more consistent and improved API :)

Introduce order for pixel exctraction

329ac5e

Ivanidzo4ka requested review from yaeldekel and zeahmed February 18, 2019 23:06

Ivanidzo4ka commented Feb 18, 2019

View reviewed changes

Ivan Matantsev added 5 commits February 18, 2019 15:25

shuffle defaults to estimator, slightly better comments

2a4deb1

make it build

aadf930

make it build part 2

1a17ee0

Merge branch 'master' into Ivanidze/ImagePixelExtractorOrder

0a1b626

Entrypoints test

af9b968

merge with master

f91bc44

Ivanidzo4ka changed the title ~~[WIP] Introduce order for pixel extraction~~ Introduce order for pixel extraction Feb 22, 2019

fix entrypoints

63081f2

Ivanidzo4ka commented Feb 22, 2019

View reviewed changes

Ivan Matantsev added 2 commits February 22, 2019 11:52

update wording

df4e9fa

order/scale

cee009e

Ivanidzo4ka requested a review from artidoro February 22, 2019 20:56

artidoro reviewed Feb 22, 2019

View reviewed changes

zeahmed reviewed Feb 22, 2019

View reviewed changes

artidoro reviewed Feb 22, 2019

View reviewed changes

artidoro reviewed Feb 23, 2019

View reviewed changes

All that harsh feedback!

f9814b6

artidoro reviewed Feb 23, 2019

View reviewed changes

two spaces

0a3d5d3

artidoro reviewed Feb 23, 2019

View reviewed changes

more changes

7e0140b

zeahmed approved these changes Feb 23, 2019

View reviewed changes

artidoro approved these changes Feb 23, 2019

View reviewed changes

Ivan Matantsev added 3 commits February 23, 2019 16:08

Merge branch 'master' into Ivanidze/ImagePixelExtractorOrder

eec5c6d

One curly boy

55e6ad0

different name for model

ff9aa7d

Ivanidzo4ka merged commit 850559f into dotnet:master Feb 25, 2019

Ivanidzo4ka mentioned this pull request Mar 13, 2019

Enable specifying order of channels in Pixel Extractor #746

Closed

ghost locked as resolved and limited conversation to collaborators Mar 24, 2022

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Introduce order for pixel extraction #2602

Introduce order for pixel extraction #2602

Ivanidzo4ka commented Feb 18, 2019 •

edited

Loading

Ivanidzo4ka Feb 18, 2019 •

edited

Loading

Ivanidzo4ka Feb 18, 2019 •

edited

Loading

codecov bot commented Feb 19, 2019 •

edited

Loading

Ivanidzo4ka Feb 22, 2019 •

edited

Loading

Ivanidzo4ka Feb 22, 2019 •

edited

Loading

artidoro Feb 22, 2019 •

edited by Ivanidzo4ka

Loading

artidoro Feb 22, 2019 •

edited by Ivanidzo4ka

Loading

artidoro Feb 22, 2019

artidoro Feb 22, 2019 •

edited by Ivanidzo4ka

Loading

zeahmed Feb 22, 2019 •

edited

Loading

zeahmed Feb 22, 2019 •

edited

Loading

artidoro Feb 22, 2019 •

edited by Ivanidzo4ka

Loading

zeahmed commented Feb 22, 2019 •

edited

Loading

artidoro commented Feb 22, 2019

artidoro Feb 22, 2019 •

edited by Ivanidzo4ka

Loading

artidoro Feb 23, 2019 •

edited by Ivanidzo4ka

Loading

artidoro Feb 23, 2019 •

edited by Ivanidzo4ka

Loading

artidoro Feb 23, 2019 •

edited

Loading

Ivanidzo4ka Feb 23, 2019

artidoro Feb 23, 2019

artidoro Feb 23, 2019 •

edited by Ivanidzo4ka

Loading

Ivanidzo4ka Feb 23, 2019

Ivanidzo4ka Feb 23, 2019

artidoro Feb 23, 2019 •

edited

Loading

Ivanidzo4ka Feb 23, 2019

artidoro Feb 23, 2019

artidoro Feb 23, 2019

Ivanidzo4ka Feb 23, 2019

Ivanidzo4ka commented Feb 23, 2019

zeahmed left a comment

artidoro commented Feb 23, 2019

artidoro commented Feb 23, 2019

artidoro left a comment

	pixel = Color.FromArgb(
	ex.Alpha ? (int)Math.Round(alpha * scale - offset) : 0,
	(int)Math.Round(red * scale - offset),
	(int)Math.Round(green * scale - offset),
	(int)Math.Round(blue * scale - offset));

Introduce order for pixel extraction #2602

Introduce order for pixel extraction #2602

Conversation

Ivanidzo4ka commented Feb 18, 2019 • edited Loading

Ivanidzo4ka Feb 18, 2019 • edited Loading

Choose a reason for hiding this comment

Ivanidzo4ka Feb 18, 2019 • edited Loading

Choose a reason for hiding this comment

codecov bot commented Feb 19, 2019 • edited Loading

Codecov Report

Ivanidzo4ka Feb 22, 2019 • edited Loading

Choose a reason for hiding this comment

Ivanidzo4ka Feb 22, 2019 • edited Loading

Choose a reason for hiding this comment

artidoro Feb 22, 2019 • edited by Ivanidzo4ka Loading

Choose a reason for hiding this comment

artidoro Feb 22, 2019 • edited by Ivanidzo4ka Loading

Choose a reason for hiding this comment

Choose a reason for hiding this comment

artidoro Feb 22, 2019 • edited by Ivanidzo4ka Loading

Choose a reason for hiding this comment

zeahmed Feb 22, 2019 • edited Loading

Choose a reason for hiding this comment

zeahmed Feb 22, 2019 • edited Loading

Choose a reason for hiding this comment

artidoro Feb 22, 2019 • edited by Ivanidzo4ka Loading

Choose a reason for hiding this comment

zeahmed commented Feb 22, 2019 • edited Loading

artidoro commented Feb 22, 2019

artidoro Feb 22, 2019 • edited by Ivanidzo4ka Loading

Choose a reason for hiding this comment

artidoro Feb 23, 2019 • edited by Ivanidzo4ka Loading

Choose a reason for hiding this comment

artidoro Feb 23, 2019 • edited by Ivanidzo4ka Loading

Choose a reason for hiding this comment

artidoro Feb 23, 2019 • edited Loading

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

artidoro Feb 23, 2019 • edited by Ivanidzo4ka Loading

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

artidoro Feb 23, 2019 • edited Loading

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Ivanidzo4ka commented Feb 23, 2019

zeahmed left a comment

Choose a reason for hiding this comment

artidoro commented Feb 23, 2019

artidoro commented Feb 23, 2019

artidoro left a comment

Choose a reason for hiding this comment

Ivanidzo4ka commented Feb 18, 2019 •

edited

Loading

Ivanidzo4ka Feb 18, 2019 •

edited

Loading

Ivanidzo4ka Feb 18, 2019 •

edited

Loading

codecov bot commented Feb 19, 2019 •

edited

Loading

Ivanidzo4ka Feb 22, 2019 •

edited

Loading

Ivanidzo4ka Feb 22, 2019 •

edited

Loading

artidoro Feb 22, 2019 •

edited by Ivanidzo4ka

Loading

artidoro Feb 22, 2019 •

edited by Ivanidzo4ka

Loading

artidoro Feb 22, 2019 •

edited by Ivanidzo4ka

Loading

zeahmed Feb 22, 2019 •

edited

Loading

zeahmed Feb 22, 2019 •

edited

Loading

artidoro Feb 22, 2019 •

edited by Ivanidzo4ka

Loading

zeahmed commented Feb 22, 2019 •

edited

Loading

artidoro Feb 22, 2019 •

edited by Ivanidzo4ka

Loading

artidoro Feb 23, 2019 •

edited by Ivanidzo4ka

Loading

artidoro Feb 23, 2019 •

edited by Ivanidzo4ka

Loading

artidoro Feb 23, 2019 •

edited

Loading

artidoro Feb 23, 2019 •

edited by Ivanidzo4ka

Loading

artidoro Feb 23, 2019 •

edited

Loading