his README.txt file was generated on <20210830> by <Pengcheng Zhang>

#
# General instructions for completing README: 
# For sections that are non-applicable, mark as N/A (do not delete any sections). 
# Please delete all commented sections after you completed this README . 
#

-------------------
GENERAL INFORMATION
-------------------

1. Title of Dataset: Project dataset

#
# Authors: Include contact information for at least the 
# first author and corresponding author (if not the same), 
# specifically email address and faculty. 
# Contact information for all authors is preferred.
#

2. Author Information
<create a new entry for each additional author>

First Author Contact Information
    Name: Pengcheng Zhang
    Faculty: Li Ka Shing Faculty of Medicine
    Email: u3005061@connect.hku.hk



Corresponding Author Contact Information
    Name:N/A
    Faculty:N/A
    Email:N/A


Author Contact Information (if applicable)
    Name:
    Faculty:
    Email:


---------------------
DATA & FILE OVERVIEW
---------------------

#
# Directory of Files in Dataset: List and define the different 
# files included in the dataset. This serves as its table of 
# contents. 
#

Directory of Files: 
   A. Filename:        PD1
      Short description:  Metabolic parameters of mice with HFD feeding   


        
   B. Filename:        PD2
      Short description:  Molecular evaluation of mice with HFD feeding   


        
   C. Filename:        PD3
      Short description: Metabolic and mlecular parameters of mice treated with ER stress inhibitors


Additional Notes on File Relationships, Context, or Content 
(for example, if a user wants to reuse and/or cite your data, 
what information would you want them to know?):              


#
# File Naming Convention: Define your File Naming Convention 
# (FNC), the framework used for naming your files systematically 
# to describe what they contain, which could be combined with the
# Directory of Files. 
#

File Naming Convention: project dataset (PD) 


#
# Data Description: A data description, dictionary, or codebook
# defines the variables and abbreviations used in a dataset. This
# information can be included in the README file, in a separate 
# file, or as part of the data file. If it is in a separate file
# or in the data file, explain where this information is located
# and ensure that it is accessible without specialized software.
# (We recommend using plain text files or tabular plain text CSV
# files exported from spreadsheet software.) 
#

-----------------------------------------
DATA DESCRIPTION FOR: [FILENAME]
-----------------------------------------
<create sections for each dataset included>


1. Number of variables:N/A


2. Number of cases/rows: N/A


3. Missing data codes:N/A
        Code/symbol        Definition
        Code/symbol        Definition


4. Variable List

#
# Example. Name: Gender 
#     Description: Gender of respondent
#         1 = Male
#         2 = Female
#         3 = Transgender
#	      4 = Nonbinary
#		  5 = Other gender not listed 
#		  6 = Prefer not to answer
#

    A. Name: <variable name>
       Description: <description of the variable>
                    Value labels if appropriate


    B. Name: <variable name>
       Description: <description of the variable>
                    Value labels if appropriate

--------------------------
METHODOLOGICAL INFORMATION
--------------------------

#
# Software: If specialized software(s) generated your data or
# are necessary to interpret it, please provide for each (if
# applicable): software name, version, system requirements,
# and developer. 
#If you developed the software, please provide (if applicable): 
#A copy of the software’s binary executable compatible with the system requirements described above. 
#A source snapshot or distribution if the source code is not stored in a publicly available online repository.
#All software source components, including pointers to source(s) for third-party components (if any)

1. Software-specific information:N/A
<create a new entry for each qualifying software program>

Name:N/A
Version:N/A
System Requirements:N/A
Open Source? (Y/N): N/A

(if available and applicable)
Executable URL:N/A
Source Repository URL:N/A
Developer:N/A
Product URL:N/A
Software source components:N/A


Additional Notes(such as, will this software not run on 
certain operating systems?):N/A


#
# Equipment: If specialized equipment generated your data,
# please provide for each (if applicable): equipment name,
# manufacturer, model, and calibration information. Be sure
# to include specialized file format information in the data
# dictionary.
#

2. Equipment-specific information:N/A
<create a new entry for each qualifying piece of equipment>

Manufacturer:N/A
Model:N/A

(if applicable)
Embedded Software / Firmware Name:
Embedded Software / Firmware Version:
Additional Notes: