Adjusted mean and mean test for multiple regression in R

By -

I formed a multiple linear regression model:

corona_soz <- lm(LZ~age  + belastet_SZ + belastet_SNZ + guteSeiten_SZ + guteSeiten_SNZ + Zufriedenh_EW + Zufriedenh_BZ + SES_3, data = MF, subset = (sex == 1))
summary(corona_soz)

For this model, I would like to calculate the adjusted mean. For this I have already used the package emmeans. I would like to calculate the adjusted mean for the respective sex (men: sex == 1, women: sex == 2). For this, I also formed an extra regression model again, since sex is already included in the subset in the model above.

mean_MF <- lm(LZ~age  + belastet_SZ + belastet_SNZ + guteSeiten_SZ + guteSeiten_SNZ + Zufriedenh_EW + Zufriedenh_BZ + SES_3, data = MF)
summary(mean_MF)

Then I wanted to calculate the mean value:

emmeans(mean_MF, ~ sex)

And received the following message:

> emmeans(mean_MF, ~ sex)
Error in emmeans(mean_MF, ~sex) : 
  No variable named sex in the reference grid

Is there any other way or simple solution for this? I have also tried various other ways, but unfortunately do not understand where the problem lies.

In addition, I would like to perform a mean test to determine significant differences in the mean values (mean and adjusted mean) and unfortunately I can't find anything suitable.

! How do I handle it if I want to get the emmeans from 3 expressions instead of 2 as in the example above (sex: males == 1, females ==2)? So f.e. the number of children coded as follows (Kinder_A):

  • 1child: 1
  • 2 children: 2
  • ≥3 children: 3
> F_AKind_scor <- lm(LZ~age + belastet_SZ + belastet_SNZ + guteSeiten_SZ + guteSeiten_SNZ + Zufriedenh_EW + Zufriedenh_BZ + SES_3 + Kinder_A, data = Frauen)

Because when I run the code, I only get one EEM instead of 3 EEM's for my 3 expressions (1,2,3).

> emmeans(F_AKind_scor, ~ Kinder_A)
 Kinder_A emmean     SE    df lower.CL upper.CL
      1.2   6.96 0.0223 11415     6.92        7

In addition, I would like to perform a mean test to determine significant differences in the mean values (mean and adjusted mean) and unfortunately I can't find anything suitable.



Comments

Post a Comment

Popular posts from this blog

Today Walkin 14th-Sept

By -
Image
14th Sept 2017 ( GO Through all List) Read Walkin details properly , Try to call company before attending if possible !!! ==================================== 1. Myntra through fresherworld (Call Based , Venue shared to shortlisted candidates) _____________________________ 2. Magna : Hiring for Client Harman : C++
Read more

Spring Elasticsearch Operations

By -
Elasticsearch Operations Spring Data Elasticsearch uses two interfaces to define the operations that can be called against an Elasticsearch index. These are ElasticsearchOperations and ReactiveElasticsearchOperations. Whereas the first is used with the classic synchronous implementations, the second one uses reactive infrastructure. The default implementations of the interfaces offer: Read/Write mapping support for domain types. A rich query and criteria api. Resource management and Exception translation. ElasticsearchTemplate The ElasticsearchTemplate is an implementation of the ElasticsearchOperations interface using the Transport Client. @Configuration public class TransportClientConfig extends ElasticsearchConfigurationSupport {   @Bean   public Client elasticsearchClient() throws UnknownHostException {                      Settings settings = Settings.builder().put("cluster.name", "elasticsearch")....
Read more

Hibernate Search - Elasticsearch with JSON manipulation

By -
Elasticsearch with JSON manipulation Elasticsearch ships with many features. It is possible that at some point, one feature you need will not be exposed by the Search DSL. To work around such limitations, Hibernate Search provides ways to: Transform the HTTP request sent to Elasticsearch for search queries. Read the raw JSON of the HTTP response received from Elasticsearch for search queries. Direct changes to the HTTP request may conflict with Hibernate Search features and be supported differently by different versions of Elasticsearch. Similarly, the content of the HTTP response may change depending on the version of Elasticsearch, depending on which Hibernate Search features are used, and even depending on how Hibernate Search features are implemented. Thus, features relying on direct access to HTTP requests or responses cannot be guaranteed to continue to work when upgrading Hibernate Search, even for micro upgrades (x.y.z to x.y.(z+1)). Use this at your own risk....
Read more