Hello - please include the feature where we can drop a node on top of a connection between two nodes. That feature is extremely useful!
Thanks.
1 Like
Defeinitely , With the advancement of acclerated coding learning because of chatGPT ⌠<< I recquest you to stop developing âfaultyâ deep learning integration keras and tensorflow>>
Rather humbly recquest you to make âPython Scriptâ node more seamless within the various context of data sience and deep learning coding.
Because who can not code deep learning, can not implement deep learning, what I believe.
** Just make it more seamless with all other nodes available in Knime**
** I hope knime will be data science hot cake in the market **
1 Like
Oh Boy. Boy Oâ Boy - can you not search for an item in the node output? Do we HAVE to insert a Row Filter and enter it there???
Please tell me I am doing something wrong!!!
Hi,
You can search for something in the output table using the magnifier icon on the right side of the table view.
Kind regards,
Alexander
3 Likes
phewâŚwhat a reliefâŚ
Thanks @AlexanderFillbrunn. I just didnât see itâŚ
Hey @sw1336,
yes, we are currently evaluating different strategies to handle long column names.
Regarding the search and filter buttons we are already working on a solution to fix them to the top right and not to the end of the table. This will make finding them a lot easier.
Greetings,
Daniel
1 Like
During first start of KNIME5 I selected my regular workspace and it looked like before. No new UI. But Node Repository completely empty.
ConfusingâŚ
I closed it and started again. This time selecting a new, empty, workspace and here it is, the new UI.
Thanks for the update @DanielBog!
As mentioned by notsure: The ability to pop out data tables is in my opinion essential. This is because a user spends most of their time on analyzing the output of their tables with the full focus needed, plus it enables a user to compare two data tables and hold the tables next to each other, or switch quickly between them via âAlt + Tabulatorâ short key 
3 Likes
I canât find a way to tag KNIME 5.
Missing commands in the nodes context menus
Hi, Iâm currently working on a text classification problem. To explore the available data I created a text tokenizer which produces a tag cloud.
Using the new UI Iâm missing some important commands in the nodes context menu to display the node output. When the output to be displayed is a table, there is no problem: the lower part of the screen shows the data for each output port; but when it comes to displaying images the user has not enough possibilities to customize the way the image is shown. So I had to revert back to the classic UI.
With the new UI I didnât find a way to resize or even save the resulting tag cloud as image:
Am I doing something wrong or the feature is actually missing?
Thanks,
Marco
Dear KNIMErs,
In general I really like the new sleek interface and can envision how it helps especially people new to KNIME to get up and running faster. As this is also the type of people I usually teach about KNIME, I can envision that onboarding will be much faster. Also some of the new nodes, will definitely especially care for e. g. âExcel peopleâ â that Value Lookup (or maybe shortened VLookup ) Node definitely rang a bell 
I am also fully aware that the current version I downloaded (5.0.0 from March 1st) is something like an Alpha version so lots of things are probably still in development. And sometimes it might be just me not finding the right way to do it, but that then is in itself a feedback about User Experience.
With that said, I tried to structure my feedback into three categories:
- Issues
- Suggestions
- What I like
⌠and I also tried to provide a reasoning for my comments which hopefully makes it more understandable for devs and readers.
Oh, and I liked the previous feedbacks from other KNIME users assuming that posts with a lot of hearts are considered as an upvote for those post / topics.
Letâs go âŚ
Issues
- Double clicking a node in the repository does not âaddâ it to the current workflow (if a node was selected previously).
â this slows down the workflow creation quite a bit as for an experienced KNIME user this is probably one of the standard ways to add nodes - Node labels canât be formatted
â This makes workflows less understandable. For example I bold column names if I mention them in the label (such as Sum of Costs). Additionally I put all flow variables I create e. g. in bold and red - Node repository search bar seems to be in âfuzzy modeâ by default
â as an experienced KNIMEr I know a lot of the nodes I want to use. However, this âfuzzy modeâ suggests me a lot of the nodes I donât want to see. If I search for the âOne Row to Manyâ Node I expect it to appear first, when I search for it exactly like that. This makes my workflow creation slower - I canât adjust the names of component output ports
â working more and more with components also for local workflows, descriptive output port names make my workflows much more usable, especially when sharing them with others (which I quite often do). An output port named âRevenue by Monthâ is much more understandable than âOutput Port 1â. This also should carry over to the massively enhanced Node Monitor which I really like - I couldnât figure out how to add configuration / widget nodes within an already existing component
â I tried drag and drop but somehow the config nodes simply donât appear. Only when I first create everything in the main workflow and then wrap it in a component can I use config nodes. This however is a massive step back in workflow and component creation for me. - Keyboard shortcuts (the usual ones) donât seem to work right now
â I use the keyboard quite a bit and one of my main way of moving nodes (I just need to align them, yes, I know, this is kind of OCD
) is using CTRL+SHIFT+Arrows. Slows down workflow creation for me and is less user friendly - Leaving a component seems to close it (so I have to re-open it when going back in)
â in 4.7 and prior I had the option to have both parts (the main workflow and the sub workflow in the component) open at the same time. This is more convenient for me, because sometimes you just need to jump into the other part. Not having that option slows down workflow creation for me. - Due to the fact that a node result is now ONLY visible in the enhanced Node Monitor, I also donât have the result table spec anymore.
â This was a quick go to place to look for some info about my result data (e. g. upper, lower bound) without having to use e. g. the Data Explorer Node (which basically does this and something more). Definitely a slow down in how I work with data (adding an additional node is simply more complicated than having a standard way to view the table spec) - New workflow coach, that appears, when I drag a connection to an empty space, recommends nodes with a table input also if I started dragging from a flow variable outport.
â this does not make sense to me, as I simply cannot connect any of these suggestions to e. g. a component or node that only has a flow variable output port. Confuses me. - No console or some other âplaceâ to see why a node threw an error
â this is maybe my BIGGEST issue so far. I must have a spot where I can read why something went wrong (e. g. wrong data type or column missing etc). That was a huge feature over other tools like Excel, PowerBI etc that simply say stupid stuff like âdivision by zeroâ or âreference errorâ. It does not necessarily have to be the console, could be any other window or pop or place in KNIME where I can see why a selected (!) node didnât execute - copy & paste of nodes acts strangely â the pasted objects seem to appear directly under the copied node which basically makes them invisible.
â I only discovered them when I wrapped everything in a component and that space become âunoccupiedâ (so to say). That was very confusing to me, especially because I even canât move them with CTRL+SHIFT+Arrow (see above) even if I know of this behavior. So I would expect the past action to put the pasted node slightly off of the original node (like a little bit lower and a little bit to the right, which seems to be standard behavior in a lot of applications) - Not having an Outline View
â especially when your workflows grow, this is a biggie (and I would dare to say that workflows grow pretty fast for 99% of the users as it is the nature of KNIME to have Nodes take 1 task and 1 task only). Yes, I can now zoom to the whole workflow with CTRL+2 but that is a slightly slower thing than for example simply pointing and clicking my mouse to a spot in the Outline view. This slows down the workflow creation for me. - Node repository seems to have only 4 categories: IO, Manipulation, Views, Other)
â as an experienced user I sometimes had a rough feeling where I probably would look for the matching node and then simply went through a few trial & errors. This not only massively improves âlearning the toolâ but is also a good way to approach data handling in a more explorative way. Now I have to either know the nodes or go to the Hub which also is not the most convenient way. As others have said this can be eventually done through some individual (like âadvanced modeâ) settings
Suggestions
I have only one (so far): the same search functionality as in the Node Repository would be great in the new âpopup workflow coachâ - that would massively speed up workflow creation.
What I like
- drawing backward connections from input port to output port
â this makes workflow connection faster - config and play buttons direclty above the node
â it feels like this is where they belong. Increase the speed of the workflow creation and makes the whole process feel much smoother - The execute button in the node monitor
â this is a really nice feature. As I probably look more and more in the new node monitor, having a button there to execute definitely improves my user experience (and saves mouse travel time) - Data Types in Node Monitor
â This is something I have wished for quite some time as it enables me to see immediately if I need a type conversion node or if my data is already in the right data type - search function in the Node Monitor
â great, massive improvement over some other rather improvised ways of searching for data. Love it! - snapping of connections
â I find this especially useful for the now âappearingâ flow variables as previously it sometimes was a bit of a guessing game, if I âhitâ the right corner spot. Good time improvement
Hope this helps
17 Likes
Nice @kowisoft ! When someone asks Phillip for detailed feedback at Summit, they get detailed feedback 
5 Likes
Hi all, some notes on the first impression about v5.
What I definitely like the most is the new output window. Every time when I inspected the results of an executed node - and this is for sure the most wanted action on an executed node, to inspect the results - the popup window was in the way. Now without any effort, I will always get the output presented.
Some drawbacks I discovered:
- I have a node with two output port, one special (custom) project port, and one regular table port. But in the output panel there is only the message: âThe data at the output port is not supported by any viewer.â
- I donât really understand the grouping with the node repository. I have loaded our own extensions, but I can reach the nodes only by searching the specific node names. When I type the extension name, it will be shown as a filter option, but when I click on this filter, no nodes will be displayed.
- Like kowisoft, I also miss the console or some error message window.
I would think that these issues are not principle design problems but some detail problems to get old functionality into the new design.
Question: Is there an update of the API for node developers?
Iâm excited about the final 5.0 to come!
2 Likes
The new interface is a step backward from a professional userâs point of view.
The ability to focus on the workflow and calculations in the nodes, rather than on a constantly updating data table as in Excel, is something that made KNIME a tool for serious computation, modeling, and data science.
When working with large workflows, the large data window over the whole display is annoying; on the contrary, the ability to view the data tables at different nodes is missing.
As a user of KNIME for more than ten years, I humbly recommend focusing on solving some chronic problems of the platform, rather than adding new half-baked features and breaking what works.
As an example, I would mention solving charting as a chronic problem. KNIME has about four or five different tools to plot graphs, but none that are of good quality and usable for creating professional and customizable graphs that can be exported and used in reports or publications. The new interactive graphs look cool, but theyâre not useful for serious work. Instead of adding such a new tool, it would be better to fine-tune the usability of some of the existing ones. Or better yet, give up developing a new tool and create a user-friendly interface for one of the classic libraries, e.g. Matplotlib, since Python is already embedded in KNIME.
This would save a lot of time for the user because now quality graphs have to be created with external tools - I do it with Python, for example. Yes, it can be done, but it lacks the elegance that a tool like KNIME could bring to users so their energy can be spent on data analysis rather than on needed knowledge of code syntax when they need more than a basic plot.
Serious general request - please, for version 5 and beyond, keep the option to switch to the classic view - just as there is now an option to switch to the new UI.
Thanks!
7 Likes
Software design Idea,
-
As you have started the tabbed window in knime, you can implement tableau or power bi visuals in knime tab, keeping the tableau or power bi in the backend. All tabbed windows should support some of interactive reporting option and exporting of the reports for dash and plotly.
-
There should be other features to be incorposated like PMML etc more learning transfer even for deep learning transfer, so tha ML engineer can work with the transfer. So that we can contribute in the wide range ML engineering section directly.
-
Data I/O should be more automated, it now recquire more manipulation steps then other softwares. Sometime it recquires advanced programming within knime. Even excel can handle those I/O automatically, but Knime can not detect without appropriate coding.
1 Like
A little bit off topic. One option could be to pre-configure Phyton based graphics so a user would have some flexibility but also a basic framework without too much code.
A list of the (too?) many graphic options and packages is at the end of the article
1 Like
I just reinstalled 4.7.3. It came with an embedded V. 5. I previously installed V.5 on its own and created a workplace for it. When I open the new version, thereâs no way I can see to open my V.5 workplace.
A post was split to a new topic: Version 45 Python Trouble on Mac
Hey @jakub,
thank you for your feedback. I can only focus on the visualisation part. When you are saying âyou like the new interactive graphsâ are you referring to the JavaScript views we have for several years already, or are you referring to the new (labs) views? If it is about the new (labs) views I am more than happy to hear your feedback on why you think they are not useful for serious work. If it is not about them please feel free to check them out and give us feedback.
There is a dedicated forum thread only for the new views and I am more than happy to discuss missing functionality or bugs.
Greetings,
Daniel
1 Like