nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Trace upstream to target tier

PierreloupDucroix

Hello,

I am trying to trace from a LV subnetwork all the way up to the MV subnetwork, but the trace always stops at the LV subnetwork controller and doesn't go further.

On the other hand, tracing from MV down to LV subnet is working fine.

I think this may be because the LV controllers are directional, but not sure. Wasn't the "target tier" option especially made for this purpose ?

Thanks

Trouver plus de publications taguées avec

Accepted answers

PierreloupDucroix

Right,

I'll try to relaunch my script with only one tier group for the 3 tiers, and proper ranks

before I had [name, type, tier group, subnet field, rank] :

and next :

let's see tomorrow how it goes

All comments

PierreloupDucroix

As far as I understand this figure :

It seems normal that subnetwork won't stop at subnetwork controllers unless it is specified in the subnet definition. Otherwise, tier A in the example above would stop at tier B controllers, which is not what we want in this configuration. But I could not find explicit rules about the different behaviors between hierarchical and partitioned.

MikeMillerGIS

Not really sure the expectation across tier group.

Hard to answer the modeling questions without looking at the model.

PierreloupDucroix

Hi @Mike

with the new tier group / tiers configuration, it now works as expected :

However, I had to modify my MV subnet definition to include some of the LV features (when applying the LV definition, I had an error saying that those features should be in the parent subnetwork definition).

Now the questions :

- is it normal in a hierarchical network that it is not allow tracing from a tier group to another tier group ?

- in any case, the MV subnetwork propagation stops at the subnetwork controllers. I have to manually put this in the condition barriers, is it expected in a hierarchical network ?

MikeMillerGIS

You should remove - category = subnetwork controller. That is not needed and is handled by the subnetwork. I think this is your issue.

PierreloupDucroix

My condition barriers are the followings :

- status = open

- lifecycle status != in service

- category = ground

- category = subnetwork controller

note that for some reason (Streetlight network nested in LV network) I had to create a hierarchical network composed of two tier group as follows :

- tier group "MV" with only MV subnetworks

- tier group "LV" with tiers for LV and for Streetlight

Is it possible that the trace from a tier from one group to a tier from the other group is causing the issue ?

Because after some tests, I don't have any issue tracing from LV to the target streetlight tier.

MikeMillerGIS

That looks correct. I am not really sure. What are you condition barriers? Do you have propagation configured?

PierreloupDucroix

Here are some tests :

1- Downstrem from MV to target LV -> OK (note that I had to remove the traversability "category = subnetwork controller" and activate Indeterminate flow for this to work)

2- Upstream from LV subnet controller on the MV (busbar) side -> OK

3- Upstream from LV to target MV -> KO with and without indeterminate flow and whatever I put or remove from traversability conditions.

Does the MV subnetwork definition have an impact on the way the target tier behave ?

Thanks

MikeMillerGIS

Yes this should work. You are setting the target to the MV I assume. Did you try it with and without indeterminate flow? Can you post a screen shot of the LV controller and trace settings?

Rejoindre la conversation

Les membres connectés peuvent publier, suivre les mises à jour, et plus encore. Nouveau ici ? Inscrivez-vous gratuitement.

Liens rapides

Community Help
Find useful guides, FAQs, and documents to help you navigate and make the most of Esri Community.