Can you show us the output? I can’t run it.
EDIT:
The only problem I now have is revealing outside of the boundary, and I have to say, that is probably impossible. I only have hints of that.
What do you mean by “reveal outside the border”?
Here’s one example, with random initial values between -3 and 3, with viewport between -2 and 2; values outside the viewport are mirrored back. This is 60 ellipses.
See here:
The left and right side are unfilled. It definitely would be nice if there is another expression that generates similar image, but being able to fill outside of border. But, I won’t look at finding how as basic search for solution haven’t been found, and mathematically, it’s not possible (probably).
This could be a nice design for some bohemian hippie headscarf 
1 Like
I finalized the CLI version. Just wish there was percentile-based cut though. Here’s a mixture of 3 Serendiptous Circle.
I recall a command named percentile and another that addresses percentile cuts, but maybe not what you are asking… I am not sure what you are asking…
Basically, what I’m looking for a command that cuts based on the frequency vs dimension ratio. $1 would be the parameter to find the lowest value that has a frequency higher than $1, and $2 would be the parameter to find the highest value that has a frequency higher than $2. Then, cut based on the found values. That’s something I requested on G’MIC 3.1 thread.
Like a band pass/stop? There is a bandpass command that you could use as a starting point.
bandpass:
_min_freq[%],_max_freq[%]
Apply bandpass filter to selected images.
Default values: 'min_freq=0' and 'max_freq=20%'.
Example:
[#1] image.jpg bandpass 1%,3%
Tutorial: https://gmic.eu/oldtutorial/_bandpass
That doesn’t give me the output I want. I want to cut instead. Let me see. I could try to do a custom command involving sorting, and then find the frequency of each value, and cut based on those.
The world doesn’t have enough graphics languages, so here’s a solution in “alfim”, a language I am developing. I call sercir() only once, so there is only one “circle”. It is based on code above by @mbs, but with smaller initial (xi,yi) and without wraparound.
function sercir ()
variables
WW = %[fx:w],
HH = %[fx:h],
xi = %[fx: 4 * rand() - 2],
yi = %[fx: 4 * rand() - 2],
xmin = -2,
xmax = +2,
ymin = -2,
ymax = +2,
xmult = %[fx: (%{WW}-1) / (%{xmax}-(%{xmin})) ],
ymult = %[fx: (%{HH}-1) / (%{ymax}-(%{ymin})) ],
rep = 1,
col,
row,
x = %[fx: %{xi} ],
y = %[fx: %{yi} ]
endvariables
-fill White
while %[fx: %{rep} < 1000 ] do
assign x = %[fx: %{x} - %{y}/2 ]
assign y = %[fx: %{y} + %{x}/2 ]
assign col = %[fx: (%{x}-(%{xmin})) * %{xmult} + 1 ]
assign row = %[fx: (%{y}-(%{ymin})) * %{ymult} + 1 ]
-draw "point %{col},%{row}"
assign rep = %[fx: %{rep} + 1]
endwhile
endfunction
-size 400x400 xc:Black
call sercir ()
+write x.png
3 Likes
Sounds like you’re talking about statistical relative frequency? A histogram ought to manage that…
What I understand here is what you name “frequency” is actually the “occurence”, right ?
(Frequency in image often refers to Fourier decomposition in image processing).
as @garagecoder suggests, computin the histogram is probably the key here.
But what do you want to do with the values below or above a certain occurence threshold. What value should be used to replace the old one ?
These become the values used for cut(). A partial work on this:
> gmic sp cat to_gray +pixelsort +,yx +area. 0,0 +label.. a[-3--1] c colormap. 0 sh. 2 pixelsort.. +,x,. rm.
The first channel is the value of image, the second channel is the occurence, and the third channel is the label value of the image. If the occurence is greater or equal to 5% starting from the left, then corresponding image pixel value becomes the cut value 1. If the occurence is greater or equal to 5% starting from the right, then the corresponding image pixel value becomes the cut value 2. So, with those found value, it is the cut values.
I have done something similar for tone re-mapping (the ranking and smoothing). The challenge is making it fast. E.g., colormap on large colourful images takes a while to process.
The speed issue is why I brought it up. I also think something like this could also apply to the math parser on a vector as well.
Beautiful name! If you replace “m” with “o” then you get my first name 
I’m interested. Could you tell us a bit more about it? Design and goals ?
It has similarities with IM syntax… Is it its own thing or using IM?
I guess that maybe, it is intended to be an extension to the IM syntax, that will be available for future versions of IM. That is really interesting.
1 Like