Hierarchical taxonomy list with transformated links

I have two functions displaying a term list of the selected taxonomy:

First function:

$  terms = get_the_terms(get_the_ID(), 'MY_TAXONOMY'); if (!is_wp_error($  terms) && !empty($  terms)) {     foreach ($  terms AS $  term) {         $  name = $  term->name;         $  link = add_query_arg('fwp_typ', FWP()->helper->safe_value($  term->slug), 'https://www.MYWEBSITE.com/');         echo "<a href='$  link'>$  name</a><br />";     } }        

Second function:

    global $  post;     $  taxonomy = 'MY_TAXONOMY';     $  terms = wp_get_post_terms( $  post->ID, $  taxonomy, array( "fields" => "ids" ) );     if( $  terms ) {         echo '<?ul>';         $  terms = trim( implode( ',', (array) $  terms ), ' ,' );         wp_list_categories( 'title_li=&taxonomy=' . $  taxonomy . '&include=' . $  terms );         echo '<?/ul>';     }  

The first one ignores the hierarchy, but transforms the links as I need, i.e. so that they lead to queries of the WP’s Facet Plugin. I understand that this line is key here:

$  link = add_query_arg('fwp_typ', FWP()->helper->safe_value($  term->slug), 'https://www.MYWEBSITE.com/');  

The second one includes the hierarchy, but the links don’t lead where I would like. How do I make this second function transform links like the first one?

Creating a hierarchical graph

To test some procedures, I am trying to create “toy models” of graphs with communities present. I want to create two distinct types of graphs: “flat” and hierarchical.

Hierarchical graphs should have clusters which form clusters among them (for example, page 41 of this presentation: http://www2.cs.uh.edu/~chengu/Teaching/Spring2013/Lecs/Lec15.pdf ). Flat graphs should have a cluster structure but with no hierarchy.

My idea so far is to create flat graphs with networkx.connected_caveman_graph (python), and hierarchical graphs by joining a number of these flat graphs, but I am unsure this is the best approach.

If it helps to know, I want to create such graphs to test a model which distinguishes between hierarchical and flat graphs.

I hope I made myself clear, and that this question is not out of place here. Thanks!

Hierarchical nodes management

We want to start managing hierarchical relationships between products using (hopefully) boilerplate tree algoritms, datamodel and GUI software (involving Java and Angular).

Verticaly bound products will limit child nodes to have a price higher then a parent (or within a % % upper limit).

Nodes on a same level AND which are manually bound to each other are considered ‘horizontically’ bound and will give the same sales price to each other (according to a ‘horizontal’ rule which uses ‘lowest’ or ‘average’ or ‘most common’ price.

We only support ‘x’ hierarchy levels (like 3 or 4)

Does these type of requirements feel familiar to some one? Can you refer me some existing documentation (database models) or existing software (Java backend and/or angular JavaScript libraries)?

Hierarchical vs Flat sitemap

I want to create a sitemap for my e-commerce website.

On the home page, there is a multi-level menu like this:

enter image description here

User can click on any of the following links from the Home Page:

  1. Fashion: enter fashion department
  2. Fashion > *Women: enter the Women‘s sub-department under Fashion
  3. Fashion > women > Shoes -> enter shoes unit under women

There are also pages link Help and About Us that use can navigate to from Home Page.

With respect to SEO, which is the better way to create a site-map?

enter image description here

So user have 2 ways to navigate to Women‘s sub-department, either directly through Home page or by navigating from Home to Fashion and then to Women page.

Hierarchical list for selecting an element

The user is trying to select an element which will be used in a form. So it could be like selecting interests in an app where you can pick the more general case (e.g. sports) or the more specific (e.g. baseball).

I have hierarchical data where:
* Exactly one node may be selected.
* Users can select nodes anywhere in the tree
* Leaf nodes must be selectable
* Parent nodes may be selectable. Selecting a parent node represents a selection of all of its leaf node descendants.
* Selectable parent nodes are uncommon.
* The depth of the data is deeper than can be readily shown on the screen all at once.

I am developing an interface for browsing this data. This data needs to be usable on both desktop and mobile interfaces on the web.

I am thinking of modeling an interface after what Apple does with hierarchical menus, like the one below. The differences in my case are primarily that:
* The items can have three states: selectable node, refinable node, and nodes with both capabilities. How do I make this look uncluttered?
* My design must operate reasonably on both desktop and mobile. How do I design the refinement signifier in an unobtrusive way that is clear even on desktop views.
* My lists have a lot of heterogenous content. This happens only rarely in Apple menus, like the shut down button in the second screenshot. How do I show heterogenous content without looking disjoint?
iOS settings menu

Notice the blue row at the bottom representing differing content.
iOS shut down screen

What I’ve been thinking of so far is similar to the Apple design. These next two screenshots show the top level of the hierarchy here, and…
Top level of hierarchy

…the screen after food is selected.
Refinement of hierarchy

I like the multi-screen approach to this design for my use case, so I am primarily looking for feedback on exactly what icons/buttons to put in, and how to separate out content. I’m particularly interested in examples on the web and high fidelity mock examples, but I’m open to lower fidelity feedback as well.

The one structural thing that I think could be changed is in the combination case where a parent node can also be selected. Conceptually I’ve illustrated it here:
Alternate design to combination case

I’d like to draw attention to the fact that this makes the rows less crowded, and seem more homogenous. But I’m not sure exactly how to design the current level selection mechanism. How could I clearly indicate that the current level can be selected? Relatedly, how do I indicate the situation where the current level can’t be selected?

How to model hierarchical json in Java

I’m a front end developer who is brand new to backend development. My task is to model json in a Java object. It’s just some mock data for now that my controller returns.

{ "data": {     "objectId": 25,     "columnName": [         "myCategory",         "myCategoryId"     ],     "columnValues": [         [             "Category One",             1         ],         [             "Category Two",             2         ],         [             "Category Three",             3         ],         [             "Category Four",             4         ],         [             "Category Five",             5         ]     ] } 


And here’s my attempt. The controller returns this json correctly. But isn’t this too simple? What I believe should be done is extrapolate the columnName and columnValues arrays into separate classes but I’m not sure how.

package com.category;  import java.util.List;  public class MyObjectData {     private int objectId;     private List columnName;     private List columnValues;      public int getObjectId() {         return objectId;     }     public void setObjectId(int objectId) {         this.objectId = objectId;     }      public List getColumnName() {         return columnName;     }      public void setColumnName(List colName) {         this.columnName = colName;     }      public List getColumnValues() {         return columnValues;     }      public void setValues(List values) {         this.columnValues = values;     }  } 

Regarding the columnNames and columnValues, I feel like I should be doing something like this in the model instead:

private List<ColumnNames> columnNames;     private List<ColumnValues> columnValues;      public List<ColumnNames> getColumnNames() {         return columnNames;     }      public void setColumnNames(List<ColumnNames> columnNames) {         this.columnNames = columnNames;     }      public List<ColumnValues> getColumnValues() {         return columnValues;     }      public void setColumnValues(List<ColumnValues> columnValues) {         this.columnValues = columnValues;     } 

And then I’d have two separate classes for them like this:

package com.category;  import java.util.List;  public class ColumnName {      private String columnName;      public String getColumnName() {         return columnName;     }      public void setColumnName(String columnName) {         this.columnName = columnName;     }  }  package com.category;  import java.util.List;  public class ColumnValue {      private String columnValue;     private int columnValueId;      public String getColumnValue() {         return columnValue;     }      public void setColumnValue(String columnValue) {         this.columnValue = columnValue;     }      public String getColumnValueId() {         return columnValueId;     }      public void setColumnValueId(int columnValueId) {         this.columnValueId = columnValueId;     }  } 

I feel like I have all the right pieces but just not sure if this is a better approach than my initial attempt…which works. Just looking for input. Thanks in advance.

Differences between enumeration-based and hierarchical token typing

When writing a lexer/parser, why/when would an advised developer chose to define the tokens’ types through an enumeration field/type hierarchy?

Image: Left: a Token class using a TokenType enumeration, right: an abstract Token class and its derivatives.

The closest question I’ve found here so far was Lexing: One token per operator, or one universal operator token? by Jeroen Bollen, but it seems to be more about the ideal deepth of the token type hierarchy.

As for my personal experience I’ve used Newtonsoft.Json‘s reader, which uses an enumeration, and I’ve read about C#’s Expression types, which seem to use a hierarchy, but also seem to be more than just tokens.

Hierarchical Bayes Model

I am given a zip-inflated Poisson (ZIP) model, where random data $ X_1, .., X_n$ are of the form $ X_i=R_iY_i$ , where the $ Y_i$ ‘s have Poisson distribution ($ \lambda$ ) and the $ R_i$ ‘s have Bernoulli distribution ($ p$ ), and all independent from each other. If given an outcome $ x = (x_1, .., x_n)$ , the objective is to estimate both $ \lambda$ and $ p$ .

We can use a hierarchical Bayes model:

$ p$ ~ Uniform(0,1) (prior for $ p$ ),
$ (\lambda|p)$ ~ Gamma(a,b) (prior for $ \lambda$ ),
$ (r_i|p, \lambda )$ ~ Bernoulli($ p$ ) independently (from the model above),
$ (x_i|r, \lambda, p )$ ~ Poisson($ \lambda r_i$ ) independently (from the model above)

Since $ a$ and $ b$ are known parameters, and $ r = (r_1,…,r_n)$ , it follows that

$ f(x,r, \lambda, p) = \frac{b^\alpha \lambda^{\alpha-1} e^{-b \lambda}}{\Gamma(\alpha)} \prod_{i=1}^n\frac{e^{-\lambda r_i} (\lambda r_i)^{x_i}}{x_i!} p^{r_i}(1-p)^{1-r_i}$

My question is to obtain the following:

1) $ \lambda|p,r,x\sim Gamma(a+ \sum_{i}x_i, b+ \sum_{i}r_i)$
2) $ p|\lambda,r,x\sim Beta(1+ \sum_{i}r_i, n+1 – \sum_{i}r_i)$
3) $ r_i|\lambda,p,x \sim Bernoulli(\frac{pe^{- \lambda}}{pe^{- \lambda}+(1-p)I{\{x_i=0}\}})$

for 1) and 2), I am able to deduce them by integrating and removing the other variables. However, for 3), I was not able to do so and eventually obtained the following expression:

$ e^{\lambda \sum r_i} r_i^{\sum x_i} p^{\sum r_i} (1-p)^{n-\sum r_i}$

Can anyone show me if what I did it correct and perhaps how to obtain the required expression?

Thank you.

Hierarchical Deterministic (HD) Importing Funds

I’m creating derived addresses from a HD private key.

I have all data saved, such as the; seed, HD private key and derived addresses with their private keys, plus wif formats.

I’m receiving funds in each address, but need a way to import all the funds as efficiently as possible into a SPV wallet. At the moment I import each address wif to recieve its corresponding balance.

Is there a neat way to pull in all funds that derive from a “master key”. Or, have I misunderstood deterministic benefits – am I trying achieve a non existent feature?

TLDR; what’s the best way to import funds from multiple addresses?