uvm_sequence_item doesn't have a logger method

[Amirk97]

I'm not sure if this is intentional or if It just hasn't been implemented yet, so not necessarily an issue, but the sequence_item class, and I think uvm_object class overall doesn't have a reporting logger class.

[raysalemi]

There are no reporting classes in pyuvm. I leveraged the logging module.

[ktbarrett]

Sounds like this is resolved, reopen if you have further argument for this feature. The Python logging library, with all its faults, is rather well understood by Python devs and sufficient, so I think it does a great stand-in for any logging system.

[Amirk97]

I think there can be further argument, well, the logger method exists in all uvm_component classes but doesnt exist in uvm_object classes, so the issue that it causes is the lack of uniformity in reporting and printing, also the log methods in components prints out the hierarchy which is nice but all of this doesnt exist in any class that's inherited from uvm_object parent, so the user is forced to fall back on using python print functions, for example it leads to printed messages like this:

" 70.00ns INFO ../IIR/Python_tb/scoreboard.py(17) [uvm_test_top.env.scoreboard]: With the observed inputs: 5187772 and 21, output: 5146216
70.00ns INFO ../IIR/Python_tb/scoreboard.py(18) [uvm_test_top.env.scoreboard]: The expected output is 5146216
80.00ns INFO ..nts/IIR/Python_tb/monitor.py(27) [uvm_test_top.env.agent.monitor]: Observed input: 7469320
80.00ns INFO ..ents/IIR/Python_tb/driver.py(28) [uvm_test_top.env.agent.driver]: Drove the item in driver
Sent the item from sequence
enable_change is 0
"

last two lines being from a sequence and the other one from item. It just breaks the uniformity and readability and also lacks the hierarchy information. This is not the case in SV UVM, would be nice if objects could also have the logger method.

[raysalemi]

The thing is, there is no hierarchy in sequences. So the UVM logging system has no provisions for it since there is no hierarchy.

A user can solve this by passing the handle of the driver or other component to the sequence. Then the sequence can use the logging methods in the component.

[Amirk97]

Right yes that can also be a solution, I think it just would be a nice thing if it had it by default since in sv uvm you can use the uvm_info without problem in uvm_objects but the same isn't true for the counterpart in pyuvm.

[raysalemi]

The uvm_report type functions in pyuvm are just convenience routines for managing logging in the hierarchy. So it doesn't make sense to put them in uvm_object since there is no hierarchy.

You're welcome to propose a solutions, and if it acts like it does in SV-UVM I'd be open to looking at it.