Update rCSI-indicator.sps #205
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
ValerioGiuffrida
requested changes
Oct 17, 2025
Comment on lines
+26
to
+38
| *** Check individual strategies | ||
|
|
||
| FREQUENCIES VARIABLES=rCSILessQlty rCSIBorrow rCSIMealNb rCSIMealSize rCSIMealAdult | ||
| /FORMAT=NOTABLE | ||
| /STATISTICS=MINIMUM MAXIMUM MEAN. | ||
|
|
||
| *** Harmonize Data Quality Guidance measures | ||
| *** Clean impossible values | ||
|
|
||
| RECODE rCSILessQlty rCSIBorrow rCSIMealNb rCSIMealSize rCSIMealAdult (LOWEST THRU -1 = SYSMIS). | ||
| RECODE rCSILessQlty rCSIBorrow rCSIMealNb rCSIMealSize rCSIMealAdult (8 THRU HIGHEST = SYSMIS). | ||
| EXECUTE. | ||
|
|
There was a problem hiding this comment.
Suggest to move to logical cleaning
Comment on lines
45
to
54
| *** Harmonize Data Quality Guidance measures | ||
| *** Check that rCSI is between 0-56 | ||
|
|
||
| DESCRIPTIVES VARIABLES=rCSI | ||
| /STATISTICS=MEAN STDDEV MIN MAX. | ||
|
|
||
| *** Clean any impossible FCS values | ||
|
|
||
| RECODE rCSI (LOWEST THRU -1 = SYSMIS). | ||
| RECODE rCSI (56 THRU HIGHEST = SYSMIS). |
There was a problem hiding this comment.
Given the variable construction, this is redundant to apply.
Comment on lines
+57
to
+86
| *** Flagging potential Data Quality issues. If any cases reflected here, refer to the Data Quality Guidance note page 31. This can be found on the VAM Ressource Centre, | ||
| *** Note that having a low rCSI is likely not a data quality issue if the area surveyed is relatively food secure | ||
| *** Note that having a high rCSI can be real if the area surveyed is very food insecure | ||
|
|
||
| COMPUTE rCSI_flag_low = 0. | ||
| IF (rCSI LE 3) rCSI_flag_low = 1. | ||
| VARIABLE LABELS rCSI_flag_low "rCSI has low values that could be a Data Quality issue unless the population surveyed is generally food secure. Flag to team leader if poor or boderline FCS". | ||
| VALUE LABELS rCSI_flag_low | ||
| 0 "No" | ||
| 1 "Yes". | ||
|
|
||
| COMPUTE rCSI_flag_high = 0. | ||
| IF (rCSI GE 42) rCSI_flag_high = 1. | ||
| VARIABLE LABELS rCSI_flag_high "rCSI has high values that could be a Data Quality issue unless the population surveyed is generally food insecure. Flag to team leader if acceptable FCS, low levels of livelihood coping etc". | ||
| VALUE LABELS rCSI_flag_high | ||
| 0 "No" | ||
| 1 "Yes". | ||
|
|
||
| *** Check flagged cases | ||
| *** If it is found that flags might be data quality issues (i.e. high number of flag_low in very food insecure areas or flag_high in seeminly food secure areas), | ||
| it is recommended to do a crosstab to see the frequency by enumerator to understand if flags are coming from the same few enumerators | ||
|
|
||
| FREQUENCIES VARIABLES=rCSI_flag_low rCSI_flag_high | ||
| /ORDER=ANALYSIS. | ||
|
|
||
| *** Check distribution of final categories | ||
|
|
||
| FREQUENCIES VARIABLES=rCSI | ||
| /FORMAT=NOTABLE | ||
| /STATISTICS=MINIMUM MAXIMUM MEAN. |
There was a problem hiding this comment.
Suggest to include in outlier detection
Comment on lines
+87
to
+117
|
|
||
| *** Optional: Compute the same variable to be used directly for IPC analysis (referring to IPC phases) | ||
|
|
||
| RECODE rCSI (LOWEST THRU 3 = 1) (4 THRU 18 = 2) (19 THRU HIGHEST = 3) INTO rCSI_IPC. | ||
| VARIABLE LABELS rCSI_IPC "Official IPC Classification for rCSI". | ||
| VALUE LABELS rCSI_IPC | ||
| 1 "rCSI [0-3] - IPC Phase 1" | ||
| 2 "rCSI [4-18] - IPC Phase 2" | ||
| 3 "rCSI [>=19] - IPC Phase 3-5". | ||
| EXECUTE. | ||
|
|
||
| *** Check distribution of final categories | ||
|
|
||
| FREQUENCIES VARIABLES=rCSI_IPC | ||
| /ORDER=ANALYSIS. | ||
|
|
||
| *** Optional: Compute the same variable to be used directly for IPC analysis (referring to IPC phases) - indicating high values (potential Phase 4) | ||
|
|
||
| RECODE rCSI (LOWEST THRU 3 = 1) (4 THRU 18 = 2) (19 THRU 42 = 3) (43 THRU HIGHEST = 4) INTO rCSI_IPC_HighValues. | ||
| VARIABLE LABELS rCSI_IPC_HighValues "Informal IPC Classification indicating high values (potential Phase 4)". | ||
| VALUE LABELS rCSI_IPC_HighValues | ||
| 1 "rCSI [0-3] - IPC Phase 1" | ||
| 2 "rCSI [4-18] - IPC Phase 2" | ||
| 3 "rCSI [19-42] - IPC Phase 3" | ||
| 4 "rCSI [>42] - IPC Phase 4". | ||
| EXECUTE. | ||
|
|
||
| *** Check distribution of final categories | ||
|
|
||
| FREQUENCIES VARIABLES=rCSI_IPC_HighValues | ||
| /ORDER=ANALYSIS. |
There was a problem hiding this comment.
Suggest to include in IPC analysis dedicated script.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
No description provided.