MARA | first modular industrial robot arm , official repository | Robotics library

Your whole code is indented in the first if condition, which means it would work only if your entry string has a space in it.

On top of that, do you use quotes or double quotes when you add your argument ? Because using sys.argv[1] takes the 1st argument.

How about a simple PIVOT

Example

Based on the line your error is occurring on, it looks like you have a malformed feature list somewhere. A feature list looks like alpha=yes|beta=no. It seems like you might have something that looks like alpha=yes|beta, which is invalid.

I think the underscore by itself is a special case and should be valid, but maybe you have some other kind of filler?

You can debug this by modifying the conllu_sentence_to_doc function in conllu_to_docs.py to print the morphs value before calling doc = Doc(...).

The original code blocks after every start of a go routine by waiting for a value to be sent over the non buffered channel, in addition the channel is closed when the WaitGroup is count down, this also closed the channel for the receiving side.

Imho a general rule is:

Do not close a channel from the receiver side and do not close a channel if the channel has multiple concurrent senders.

Yes, you just have to use bot.guilds.cache.get("GUILD_ID").name instead of message.guild.name! Documentation

To change your bot nickname on server use:

• switch to Plotly Express. Need to construct dataframe that is well structured for Plotly Express
• only loop / repetition is structuring dfp
  1. your code is doing groupby()' and value_counts()` for all columns except Q7a
  2. have restructured you pandas code to be a bit simpler. Rename can be achieved through renaming the series
  3. new column q is the source column
• the legend text is a dict mapping of column name to text. Put this in dataframe as well
• then it's a simple case of building traces with px.bar()

Yes, it can be.

If you go to purchasing pricing conditions, you can find that one of the possible combinations is

67: Plant Info Record per Order Unit

So it depends on what key combination will be used in which case based on concrete order conditions, but this situation definitely can happen.

You can read more about purchasing info-records here:

https://blogs.sap.com/2013/12/27/create-info-record-for-different-order-unit/

Your question boils down to Value vs. Reference Semantics, I'll quote some parts of that article:

Reference semantics are A Good Thing. We can’t live without pointers. We just don’t want our software to be One Gigantic Rats Nest Of Pointers. In C++, you can pick and choose where you want reference semantics (pointers/references) and where you’d like value semantics (where objects physically contain other objects etc). In a large system, there should be a balance. However if you implement absolutely everything as a pointer, you’ll get enormous speed hits. Objects near the problem skin are larger than higher level objects. The identity of these “problem space” abstractions is usually more important than their “value.” Thus reference semantics should be used for problem-space objects.

In ABAP you'd model "problem-space objects" either as structures or classes, thus those are values for which one would generally use reference semantics. For referencing class instances one has to use references, which can also be used to reference structures. So for references in ABAP, one would generally use references instead of the more limited field symbols.

Now with references you usually have the problem of memory management,
as as long as a value on the heap is referenced, it cannot be garbage collected and references onto the stack can only be accessed till the stack is popped off. Thus there is always some overhead for managing the referenced memory and checking whether references are still valid. The ABAP Documentation states:

From a technical perspective, the field symbols are implemented by references or pointers, which are comparable to references in data reference variables. A data reference variable is declared in the same way as every other data object and the memory area for the reference it contains is in the data area of the ABAP program. However, the pointer assigned to a field symbol is exclusively managed by the ABAP runtime environment and is located in a memory area, which cannot be accessed directly in an ABAP program.

Additionally (local) field symbols can only be declared inside a procedure (and not e.g. as an instance member), and as such the lifetime of a field symbol is never longer than that of a local variable. This is also true for references to table lines as long as nothing is deleted from the table. These guarantees probably allow the ABAP Kernel to handle field symbols in such cases more efficiently (e.g. this discussion).

So field symbols make sense where performance is crucial and copying a structure² is way more expensive than passing around a reference (although you want to keep value semantics). The prime example for that are loops over large tables. When writing back into the table a field symbol is also easier than a MODIFY to copy back the values into the table.

TLDR: Prefer FIELD-SYMBOLS inside of loops!

²When passing around other large data objects such as internal tables or strings it would also always make sense to pass by reference instead of copying. Fortunately ABAP already does that under the hood for these types, and copies when they're mutated (to keep the value semantics).