Skip to content

Weight analysis shows too many warnings #2650

Closed

Description

@lwrage

Summary
A user reported that the weight analysis reports warnings for logical components that cannot be turned off and pollute the report.

Expected behavior
Irrelevant warnings should not be created, or it should be possible for the user to suppress them.

Steps To Reproduce

A model needs to be created that exhibits the undesirable behavior.

Desktop (please complete the following information):

  • OSATE Version: 2.8.x? 2.9.x?
  • Operating System: WIndows

Activity

  1. added this to the 2.10.0 milestone on May 7, 2021
  2. lwrage commented on May 7, 2021

    @lwrage
    ContributorAuthor

    This was taken from a report. We need to verify that this is as described.

  3. modified the milestones: 2.10.0, 2.11.0 on Sep 18, 2021
  4. removed this from the 2.11.0 milestone on Dec 14, 2021
  5. smithdtyler commented on Oct 22, 2024

    @smithdtyler

    I am experiencing this issue in OSATE 2.12

  6. added theissue type on Aug 22, 2025
  7. AaronGreenhouse commented on Aug 22, 2025

    @AaronGreenhouse
    Contributor

    Complaint is vague and does not provide an example. However, an inspection of the analysis marker output code shows two things:

    • Abstract components are assumed to have a weight — Not sure much to be done about this because the whole point is that we don't know what an abstract component could be.
    • Threads and ThreadGroups are not ignored when searching for subcomponents — This seems like a bug because PROCESS, VIRTUAL_BUS, and VIRTUAL_PROCESSOR components are ignored. (This could be because it was assumed that PROCESS would be ignored, so it would not be possible to encounter a thread or thread group.)
  8. AaronGreenhouse commented on Aug 25, 2025

    @AaronGreenhouse
    Contributor

    So, combining the two points above, there are spurious warnings when a thread group is a subcomponent of an abstract component. I have make this happen with the following example:

    package Noisy
    public
    	with SEI;
    
    	thread T
    	end T;
    	
    	thread implementation T.i
    	end T.i;
    	
    	thread group TG
    	end TG;
    	
    	thread group implementation TG.i
    		subcomponents
    			a1: thread;
    			a2: thread;
    	end TG.i;
    
    	process P
    	end P;
    	
    	process implementation P.i
    		subcomponents
    			t1: thread T.i;
    			tg1: thread group TG.i;
    	end P.i;
    
    	abstract X1		
    	end X1;
    	
    	abstract implementation X1.i
    		subcomponents
    			p: process P.i;
    			tg: thread group TG.i;
    		properties
    			SEI::NetWeight => 5.0 kg;		
    	end X1.i;
    end Noisy;
    

    When X1.i is instantiated and analyzed, there are "No net weight" warnings on subcompnents tg, tg.a1 and tg.a2.

  9. AaronGreenhouse commented on Aug 25, 2025

    @AaronGreenhouse
    Contributor

    Fixed weight analysis to also ignore threads and thread groups.

  10. added this to the 2.17.0 milestone on Aug 29, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Type

Projects

No projects

    Milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions