Create segment in Google Analytics from specific event

I may have painted myself into a corner here but, is there a way to create a segment from a specific event. I know that it is possible to create segments based on event label, action, and category, but these are not combined when creating the segment as an event.

My issue is that I want to segment based on a label in an event but I have a different event with the same label with different action and category.

I don’t want to exclude this other event from the data since that could skew the data.

Is this possible to do?

How do I set more than one target conditions in the Google Analytics Segment forms?

What I want is to include both 428x926 and 414x896 Screen Resolutions to my filter of a newly created segment.

However, after trying many times I still couldn’t figure out. I think I need to use the is one of condition, but I don’t know how should I fill in the rules.

I can’t find any reference on Google Analytics. Is there any tips for this?

Thanks

enter image description here

summation – How to average strain on segments of a string/wave to smooth out per segment strain, but not add or remove any strain overall?

I am attempting to model wave motion for example on a string or a beam using finite difference modeling, where the motion/position of any point $u(i)$ is calculated based on past positions of $u(i+1)$, $u(i)$, $u(i+1)$, etc:

enter image description here

One aspect of the model reacts to strain ($ε$), which is the lengthening of a given finite difference segment $ε = frac{ΔL}{L}$.

In a string or beam where such strain occurs, there is some nonlocal effect. Due to long fibers that extend through the structure, a stretch in one finite difference segment actually creates strain which “averages” over a longer distance.

In the most extreme case, one would simply average all the segment strains, presuming the strain is totally uniform from one end to the other. (The more realistic case is probably somewhere between, with likely I would guess a Gaussian distribution of strain around each point.)

Let’s say you have hypothetically $n$ number of points between pinned/fixed boundaries for a string. If you wanted the strain in one point $ε(i)$ to be represent a sort of average of the strain for $j$ number of points on each side, how can you calculate this average in such a way that the total strain of the system is not changed?

Ie. If the total strain is the sum of $ε(i)$ $(i = 0…n)$, how do you calculate a $ε_{avg}(i)$ for $j$ points on each side of $i$ so that this sum of strain is unchanged?

For example, if you say simply $ε_{avg}(i) = (ε(i+1) + ε(i) + ε(i-1))/3$ and use $ε=0$ for points beyond the boundaries, then sum these $ε_{avg}$ points, does it still give you the same sum of strain as if you hadn’t done the averaging?

My impression is that this changes the total strain. Ie. It does not “conserve” strain.

I am then wondering what would be a correct or mathematically reasonable way to “average” strain in this type of manner while still conserving strain so total strain over the full length is not created or destroyed.

write ahead logging – Postgresql 13 Change WAL segment size

On my Ubuntu 20 server, I installed PostgreSQL 13 using the apt manager. I read some articles on performance tuning of PostgreSQL (1) and thought of increasing the WAL segment size (from default of 16MB). I see the following instruction, however, I don’t know where to run this.

initdb -D ./data --wal-segment=1024

I guess the documentation refers to installing from PostgreSQL source code, which I don’t intend to do. How do I go about change the WAL segment size?

(1) https://software.intel.com/content/dam/develop/external/us/en/documents/Open-Source-Database-Tuning-Guide-on-3rd-Generation-Intel-Xeon-Scalable-Processors.pdf


Following Daniel’s answer, I did the following steps

pg_lsclusters
sudo pg_dropcluster --stop 13 main
sudo pg_createcluster 13 main -- --wal-segsize=256
sudo pg_ctlcluster 13 main start

python – how to plot curvature o road with road segment information?

I have the information of road segments and want to plot the curvature, but could not get reasonable results. I have this code:

import numpy as np

a = np.array((332 0 0 0 0 0 0 0)) # straight for first 5 sec
b = np.array((122 240 0 0 0 0 0)) # left for next 3 seconds
c = np.array((330 0 0 0 0 0 0 0)) # straight for next 5 seconds

plt.plot(a, b, c)
plt.show()

oracle 12c – ORA-01652 – How to reduce TEMP segment usage?

In production we have a failing batch with an error:

ORA-01652: unable to extend temp segment by 128 in tablespace MYTABLESPACE

The TEMP segment has already been increased to its maximum tolerable according to the DBA.
Indeed, the SQL request below performs so many outer joins that this behaviour is obvious…

There are two dates as inputs : from and to.

SELECT *
    /* In reality, not all columns are included but "only" the 122 required */
                    
FROM TABLE1 t1
    INNER JOIN TABLE2 t2
        ON t2.ID = t1.ID_T2
    INNER JOIN TABLE3 t3
        ON t3.ID = t1.ID_T3
    INNER JOIN TABLE4 t4
        ON t4.ID_T1 = t1.ID
    LEFT JOIN TABLE5 t5
        ON t5.ID_T1 = t1.ID
    LEFT JOIN TABLE6 t6
        ON t6.ID_T1 = t1.ID
    LEFT JOIN TABLE7 t7
        ON t7.ID_T3 = t3.ID AND t7.DATE BETWEEN TO_DATE('xxxx-xx-xx', 'YYYY-MM-DD') AND TO_DATE('yyyy-yy-yy', 'YYYY-MM-DD')
    LEFT JOIN TABLE8 t8
        ON t8.ID_T1 = t1.ID
    LEFT JOIN TABLE9 t9a
        ON t9a.ID = t4.ID_T9
    LEFT JOIN TABLE10 t10
        ON t10.ID_T4 = t4.ID
    LEFT JOIN TABLE11 t11
        ON t11.ID_T4 = t4.ID AND t11.DATE BETWEEN TO_DATE('xxxx-xx-xx', 'YYYY-MM-DD') AND TO_DATE('yyyy-yy-yy', 'YYYY-MM-DD')
    LEFT JOIN TABLE9 t9b
        ON t9b.ID = t11.ID_T9
    LEFT JOIN TABLE12 t12
        ON t12.ID_T1 = t1.ID
    LEFT JOIN TABLE13 t13
        ON t13.ID_T4 = t4.ID
    LEFT JOIN TABLE14 t14
        ON t14.ID_T13 = t13.ID
    LEFT JOIN TABLE15 t15
        ON t15.ID_T4 = t4.ID
    LEFT JOIN TABLE16 t16
        ON t16.ID_T4 = t4.ID
    LEFT JOIN TABLE17 t17
        ON t17.ID_T1 = t1.ID
    LEFT JOIN TABLE18 t18
        ON t18.ID_T17 = t17.ID
    LEFT JOIN TABLE19 t19
        ON t19.ID_T17 = t17.ID
    LEFT JOIN TABLE20 t20
        ON t20.ID_T17 = t17.ID
WHERE 
    t4.something IS NOT NULL OR t11.something IS NOT NULL
ORDER BY t2.ID, t1.ID, t3.ID, t4.ID, t14.ID, t18.ID, t5.DATE DESC;

I’m very pessimist about this issue which raises a very big conception problem. We should have split it in several steps.

Do you see a way to reduce the TEMP segment usage without a change of the code that needs the returned data as-is? For example:

  • Can a subquery performing the WHERE clause, help?
  • Can a smaller interval between the date from and to, help?

In general, what affects the TEMP segment usage?