Frontend 2: Feedback

Hi guys,

with the integration of FE2 into our deployment, a few points of feedback came to me:

  1. Filtering the types shows 0 instead of a type name


    although it is stored in the element

  2. Legend for Decimal numbers and Shuffle mode for coloring
    the filter range is already pretty good, but as the colours are also indicators to see the distribution it would be good to also show the distribution legend like for the text parameters. A legend would also help with Finite Element results.
    Additionally, it would be great to have an optional shuffle mode for the colouring so that the colour distribution is not linear but random. This helps for example if you want to check height jumps in a slab (colours of neighbour elements have more variance and you see differences faster if the elements don’t have the same z-height).

  3. Confusing tree
    This model came from Revit. We have different level options some levels as a tree others without sub-hierarchy and then all the other categories below. This will be super confusing and not helpful for the users. As mentioned in the past a tree like in the IFC would be super helpful, otherwise people will have a hard time navigating.

I’m still a big fan of the Flexible Tree, we have it now at B+G as Revit and Rhino Plugins

.
The users can structure the tree according to their needs and if they don’t want to they have a default.

  1. A section box which can be rotated like in Revit
    in case buildings are uploaded with the world coordinate system and angle

  1. Rounded decimals
    when you are showing that many decimals people will make direct assumptions (judgement in the worst case) about the inaccuracy of data which is sent to Speckle. An example is the top of the slab (Höhe oben). Rounded and three digits after the zero would be good then people don’t question the data … at least for the UI.
    image.

  2. ### Addition ###: Shared Parameters can only be searched for the filtering with the ID of the parameter, not with their name. In the old frontend it was possible to search for the real name

  3. ### Addition ###: Show volumes/area in the change comparison to understand, why this is a change … in this case the red column was deleted and the yellow one receives more m^3


If you have questions let me know! Always happy and up for a talk in case needed.

Best,
Alex

3 Likes

Good suggestions.

Not sure about this one :slight_smile:

In CAD I set 6-8 decimals - so that it jumps into my eye that something went wrong …
Better an option to deactivate trailing zeros … makes it even more flashy :slight_smile:

If you are sure it not inaccuracy in CAD and only a translation issues in upstream to
Speckle, I do agree though and second an option to set number of decimals shown.
Second, my OK for preventing clients’s judgment.
My third reason is that 12+… or so redundant zeros do not really help legibility.

For CAD this is totally fine to have this precission (alligned to the other parties helps too :slight_smile: ). In this case above, it is upstream to Speckle. As one is not able to differentiate between bad outside quality, I would round everything … because if it is already bad outside of Speckle, why should Speckle judge :wink: .

With that I agree:

At least from our point of view mostly non-CAD-users (project managers, project engineers) are accessing the viewer. If they see examples like the above, there is one or both of the scenarios below …
a) what are my people doing … this looks bad
b) Speckle is super inaccurate … please don’t use it anymore …

Scenario b) I want to prevent. It is as much a precision issue as with everything computer-based :slight_smile:.

^ I totally agree.

Just that 15,2799999999999998 triggered me.
As I so often got similar client’s geometry in the past. When I did the 3D
and snapped to their geoimetry I had to fight with boolean failings later.
And some users intentionally set tolerance to minimum decimals, to not
get bothered by own accuracy.
From this point of view I would like to make 18 decimals mandatory for
everyone in CAD environment. Maybe even mandatory use of snaps …

1 Like

Decimal accuracy, if constrained at all, should be done so in relation to the tolerances. There are ANSI or ISO(DIN) standards for all of this. Having tackled these issues a million times over my career I’d prefer to apply a standard than either round arbitrarily or allow for custom truncation.

That said the tools we use vary enormously in the ability to work to standards. Coming from a longtime love affair with microstation has spoiled me with how accurate software can be so the Revit snap to orthogonal „feature“ is the most extremely bad version of this that I recall. While the ISO standard recommends 8 decimal point values for degree angles, try being any more accurate than 2 in Revit.

Accuracy greater than required tolerance can be problematic even before we cover unit conversions or binary to decimal conversion.

These are just my thought, the team will take your suggestions into consideration.

2 Likes

Hi @AlexHofbeck,

Thank you for your feedback.
I would like to schedule a call to discuss your suggestions further. Please book a call with me at https://calendar.app.google/bmnvnjgDxJTfHZ5N6.

Looking forward to hearing from you soon!

2 Likes

additionally to the above and referring to the 1) types … it seems that parts of the elements have values others do not. I’m not sure if it is related but @samberger has a similar topic. The model was uploaded yesterday with the latest connector version.

3 Likes

Not sure if it’s related, but I posted my issue here: Revit's built-in parameter ALL_MODEL_TYPE_NAME saves NULL

As there is quite a lot of points and now follow-ups for different items on the list we might get unstuck quickly. But lest give it a shot.

What you are describing is a classic histogram; would that be a helpful solution?

What options were selected as the criteria for sending that version from Revit? Selection, Category? And what version Revit Connector are you sending with?


Me too :wink:


Noted!

Noted!

Indeed, there is perhaps both:

  1. more logical comparison points to be made on the diffing (though are you reporting that the diffing was incorrectly identifying?)
  2. an indication of the points of difference (geometry, data, metadata)
4 Likes

Unclear if it is connected to @samberger 's issue - and I’m struggling to replicate your observed behaviour, which, given that it is a screenshot, is undeniable.

Could you share privately the model?

Part of me is suspecting localization but I hope not.

Hi @jonathon,

I will also have a meeting with @Agi tomorrow maybe we can go in detail there :slight_smile:.

Here are some of the answers:

Something like this but in your style:


or in your style
image

you have a min value, you have a max value … and maybe a slider for the steps between max and min.

your latest official Connectors 2.17.0, Selection with category to only send categories: Walls, Floors, Structural Columns, Stairs, Foundations, Structural Framing.

and here:

  1. The diffing was fine … I wanted to say that volumes/quantities might be a good additional indicator for someone to check. This is not provided in the panel … might also make it too crowded. Maybe I also see it too much out of my perspective.
  2. It would be cool to have an indicator to show where the data differentiates maybe like a yellow dot … or something more visible. Maybe only show what parameters/properties are different.

Thanks and best,
Alex

1 Like

I’m adding something new here which came to @ltascheva and me while preparing a training. I don’t think that I brought this up yet @Agi

The models are arranged by latest creation. Which makes sense for dynamic exchange of models and modelparts.

In the case of a more structured approach like the above, there might be the wish of the users to have a sorting by name (addtionally to date). Otherwise, it can be really confusing, especially with lots of models and submodels.

5 Likes

Thank you @AlexHofbeck - great feedback! We’ll take care of it :sparkles:

1 Like

@Jonathan_Rabagliati a kindred spirit :smiley:

2 Likes

A familiar kindred spirit :wink: … Design Modelling Symposium Versailles 2017

4 Likes

As hyperlinks can be really useful to link documents, say you have a refurbishment project, and you reference the old scanned drawings to a model element. We figured out the following points for you as feedback

A: Hyperlinks in parameters

It would be great to have a hyperlink function for parameter values … say the parameter value is in URL formatting it makes a clickable hyperlink in the properties menu

B: Hyperlinks as part of comments
By copying hyperlinks into the comments it shows it as black text but people don’t conclude that it is clickable. It would be great to highlight the hyperlink either by underlining it or by creating a border around it.

In case you add a hyperlink as text manually it stays text and is not clickable. It would be great if it gets formatted after publishing the comment.

CC: @ltascheva @rmsantos

4 Likes

I was looking for a similar post made about URLs in comments in the legacy app. We certainly have a ticket for this, and the value is certainly appreciated.

I recalled security discussions of clickable URLs, but as I say, I can’t now find it.

Do you have any thoughts? Perhaps the collaborator role or above is a trusted source. URLs in data properties is tricker to validate the provenance of.

If I‘m not fantasizing the hyperlinks were a bit more visual in the comments of the legacy app … we were able to reference a product catalog for impact noise reduction onto a staircase and it looked clear that one could click on it. At least it was in my mind like this.

Regarding parameters and in general:
Maybe with an allow list under the admin settings … You define the URL which is allowed or blocked. By default everything is reduced/blocked

2 Likes

I will create tickets for both supporting hyperlinks in the selection info panel and in comments. We can consider any security problems when we pick them up.

2 Likes

5 posts were split to a new topic: Difficulty viewing long data values in the new web app